Related
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!
NB! Be careful when doing this manually, one wrong move and your phone might get bricked.
Manual method (not recommended):
Download the bootloader.bin (B518) from MediaFire.
Copy it to the root of your SD card.
Use a Terminal Emulator if on phone or start ADB and write in "adb shell".
Write in "su" to get root rights.
Write in "dd if=/sdcard/bootloader.bin of=/dev/block/mmcblk0p3" to copy the bootloader.bin from SD card to the bootloader partition.
All done!
Protip: When using Linux distribution, pink screen mounts your internal SD card, data, cache and system partitions. This happens because Windows does not mount extX partitions by default.
I suggest everyone to do this as long as you have rooted your phone and want to flash custom ROMs/kernels.
Now you can recreate your backups with this tutorial.
Special thanks to dancer_69, who sent me B518 bootloader.
Thank you. This is going to be useful.
Was this the more important thing than rom?
julle131 said:
Thank you. This is going to be useful.
Was this the more important thing than rom?
Click to expand...
Click to collapse
Nope
10chars
Thanks! I just test it and the trick works!
Blefish I think its better fit on Android Development
As requested
moved to Development
Used the zip file method... yes, pink screen supports usb again, but phone now boot-loops and I can't access recovery anymore. Will try to flash Stock Rom again :S ****! Will report if really bricked
EDIT: can't flash ROM anymore, and can't access recovery... I guess I'm pretty much screwed... can someone post the latest bootloader from huawei (the locked one)? I still don't know how i'm going to installed it since I can only access the pink screen and nothing more... It's really bricked isn't it?
---------- Post added at 12:40 AM ---------- Previous post was at 12:27 AM ----------
Also, my partition scheme is showing like this (I don't know how it was before). Is this normal?
http://i.imgur.com/Z3lhg.png
fjsferreira said:
Used the zip file method... yes, pink screen supports usb again, but phone now boot-loops and I can't access recovery anymore. Will try to flash Stock Rom again :S ****! Will report if really bricked
EDIT: can't flash ROM anymore, and can't access recovery... I guess I'm pretty much screwed... can someone post the latest bootloader from huawei (the locked one)? I still don't know how i'm going to installed it since I can only access the pink screen and nothing more... It's really bricked isn't it?
---------- Post added at 12:40 AM ---------- Previous post was at 12:27 AM ----------
Also, my partition scheme is showing like this (I don't know how it was before). Is this normal?
http://i.imgur.com/Z3lhg.png
Click to expand...
Click to collapse
Its not bricked, relax. Someone else will help you, I can't help via phone.
What recovery did you flash it on? I tried it several times and it worked fine. But in your case, I believe the partitions got messed up, not sure how. And when you remove battery, reinsert it after 10 secs, then try to start recovery.
Sent from my U8800
I've flashed with "official" 5.0.2.6... I know, I know, the firs post states 5.5.0.4, but i got dumb somehow... even worse, I have previously customized my partitions to have more internal space via one of those scripts that are available on the site, so maybe that was the problem.
At this point I'm installing stock rom via dload method.
It wouldn't install before, when dload folder was in the sdcard (Windows wouldn't mount phone's internal memory in pink mode, but luckily, ubuntu mounted the all the internal partitions correctly, so i copied the dload folder to the internal memory and is now in the installing phase... will report if that worked..
I guess I should have firs install recovery 5.5.0.4 in the pink screen and then try to access it, but my brain is all messed up at this moment...
bye bye, saturday night out with friends :S
EDIT: install of stock ROM (BTW, back to 2.2) completed, phone is restarting, lets see...
EDIT 1: formatting data... I guess it's working... lol
EDIT 2: new restart
EDIT 3: Successfully booted into ROM!!!
EDIT 3: In the process of installing and trying to access recovery
I still don't understand the conflict. The partition table should be then fine, if you modified it before the flash. Did you have fast boot on?
I am happy you got it fixed
Sent from my U8800
Blefish said:
I still don't understand the conflict. The partition table should be then fine, if you modified it before the flash. Did you have fast boot on?
I am happy you got it fixed
Sent from my U8800
Click to expand...
Click to collapse
No, It was off... Everything is fine now... uff, what a relief! Glad I was easier than I thought it would be ;D
EDIT: partition table seems to be fine in Ubuntu, I guess Windows or that particular partition program wasn't reporting partitions correctly...
Out with friends now
thanks
i flashed after this the mobile never boot
i have froyo 2.2.1 and the computer never see or even read my mobile
now i have the pink screen but also usb never recognize or even give me alert
what i have to do (software or hardware proplem)
thanks
salah_heart said:
thanks
i flashed after this the mobile never boot
i have froyo 2.2.1 and the computer never see or even read my mobile
now i have the pink screen but also usb never recognize or even give me alert
what i have to do (software or hardware proplem)
thanks
Click to expand...
Click to collapse
Mine also wouldn't boot, but pink screen successfully made usb storage work. Try pink screen in ubuntu and see if it mounts your partitions. Then install stock rom again with dload folder method (copied to internal memory), that worked for me...
good job 1st of all, 2 things though,
I've been wondering, .35 kernel ROMs all seem to have the same problem, phone reboots when waking up with wifi on. This is a problem in either miui, CM7 and also, official.
Which leads me to conclude that this is kernel related and probably won't be fixed until someone, (hopefully Franco) picks the kernel up for a revamp.
Are my assumptions correct?
Also, if someone is to use custom ROMs does it make any difference if we upgrade to latest official or straight from beta 1?
fjsferreira said:
Mine also wouldn't boot, but pink screen successfully made usb storage work. Try pink screen in ubuntu and see if it mounts your partitions. Then install stock rom again with dload folder method (copied to internal memory), that worked for me...
Click to expand...
Click to collapse
after i did and flashed 2.3.5 b522 but yet never my computer see my mobile
please could you make it step by step for me
i have u8800H
Whee! I knew it was doable.
Many thanks and all that.
blefish look at pm
2.2 has pink screen already unlocked, so that has nothing to do with this. This is for flashing only if you have a locked bootloader, which is the B522 ROM.
I am creating an app to backup your phone fully even if it is turned on. That way there is a chance to restore the phone if something brakes during the process.
Sent from my U8800
Blefish said:
I am creating an app to backup your phone fully even if it is turned on. That way there is a chance to restore the phone if something brakes during the process.
Click to expand...
Click to collapse
Wow!the big secret!
Sent from my u8800
Blefish said:
2.2 has pink screen already unlocked, so that has nothing to do with this. This is for flashing only if you have a locked bootloader, which is the B522 ROM.
I am creating an app to backup your phone fully even if it is turned on. That way there is a chance to restore the phone if something brakes during the process.
Sent from my U8800
Click to expand...
Click to collapse
U sir, deserve a lot of thanks for this.. I've been holding back to flash the new 2.3 ROM because its locked bootloader.. With pink screen back, flashing roms it back to getting less risky now.. TQ~!
demolition23 said:
Wow!the big secret!
Sent from my u8800
Click to expand...
Click to collapse
Nope, but for the information, it's going to be an app named X5Toolbox, and from there you can flash recoveries, boot images, bootloaders, perhaps even AMSS, restore and backup IMEI etc.
Ok, as many of you know, the only thing between custom ROMs and your phone is the fact that we can not get the ROMs that we make to flash correctly in our current CWM recovery. We either get status 0, status 1, status 6, or status 7 errors when flashing. Most of these errors directly correlate with the boot.img command line(s) in the updater script.
uoY_redruM and I have spent over ten hours a piece trying to figure this out and have made progress but are still stuck.
We soon found out that the kitchens we were using to cook our ROMs did not have the latest directory for our phones partitions and their addressess (mmcblk0p1, etc.) This directed us to where we need to look to fix this.
The critical partitions we need to make ROMs flash are
1. Data
2. System
3. Boot
4. Cache
5. (optional) SDCard
It was easy enough to find 1,2, & 4, however the boot was a little bit trickier.
There are drives on our phone that had the following IDs:
1. mmcblk0p5 aboot
2. mmcblk0p7 boot
3. mmcblk0boot1 disk
4. mmcblk0boot0 disk
We believe that the real boot partition is 7, however we have yet to get a fully functional ROM up and running, despite writing the boot.img to p7.
With certain modifications to the boot.img lines in the updater script, I have been able to flash a ROM, but upon boot I lose SU permissions and the radio is borked (does not detect SIM card). Clearly this is still not functional and is caused by the boot.img (kernel) not being included in the ROM.
Attached is a scanned copy of a list of all of the partitions in our phone, along with their ID.
This is a thread where we can easily bounce ideas off of each other and hopefully get to the root of this problem ASAP.
Let's please keep this on topic. Thanks.
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Reviewers said:
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Click to expand...
Click to collapse
Yeah, we're starting to think it's recovery related.
We've (well most he) got the ROM to boot up now....but......and that's a big but.....it reads as if we have no SIM card. So, that's where we're currently stuck.
Same place boots loads kernel but no root or radio same sim card error
Wildchld said:
Same place boots loads kernel but no root or radio same sim card error
Click to expand...
Click to collapse
Are you using an insecure boot.img?
FiveOhFox said:
Are you using an insecure boot.img?
Click to expand...
Click to collapse
yep
Built in the kitchen
---------- Post added at 06:46 PM ---------- Previous post was at 06:41 PM ----------
I think it maybe the recovery too because I have lost root on restores
Wildchld said:
yep
Built in the kitchen
Click to expand...
Click to collapse
Ok. I'm trying it with secure boot.img files to see if that has any bearing on our results but so far nothing.
Ok well I'm going to shelf working on the script for a while and instead start working on my ROM and possibly learning how to make a recovery lol.
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Reviewers said:
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Click to expand...
Click to collapse
Why are you so adamant that it's the recovery?? You don't even own the phone!
I owned the amaze before and it didn't flash with 1 recovery but it worked on another.
I know this is Samsung but another user is agreeing with me as well.
Read the thread I made in General.
Flashing something from another phone will never work 100% as made for that phone.
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
Plus when I get the phone I'll look into it as well.
I might not be much help in this area but I'll do what I can.
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
uoY_redruM said:
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
Click to expand...
Click to collapse
If you use the update-binary from the EU rom the status 6 error goes away but same results but the kernel will load. Status 6 error is a syntex error not because of the script but the binary is looking for different parameters.
Also I see no Sprint roms being dev maybe they have the same problem
One last shot before work... Attached is a working script and binary
Rom boots fine and about shows baseline unknown so maybe we need to load the radio in the rom also.
Also when I restore a nandroid radio comes back but won't connect till I turn off wifi then service returns.
Here's the thing I found odd....
If you use CWM to pull a backup, the boot.img/recovery.img are both 10MB in size.
If you use the Toolkit to pull a backup, the boot.img/recovery.img are 2MB/512KB.
Why is that? That doesn't make any sense to me. They should be duplicate but they're not.
....the only thing that comes to mind is maybe the Toolkit (since it was designed for the international phone) points to different partition points and aren't pulling the correct files? Then again, why would they be named properly?
That's where I'm at for today.
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
uoY_redruM said:
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
Click to expand...
Click to collapse
You used the recovery.img from what, again? And the script posted above writes to p18 which is recovery so that's not a problem.
So it boots but is missing radio? Do you have root?
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
uoY_redruM said:
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Click to expand...
Click to collapse
Lol your right but i have loaded this nandroid like 30 times i know its good
Sent from my SGH-T999 using Tapatalk 2
FiveOhFox said:
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
Click to expand...
Click to collapse
Found a few more files that could be of use. Five is writing up some commands to try flashing them.
I'm starting to feel really good about today!
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.
What you will need:
KingRoot V4.5.0.901 (latest version as of this posting)
Rooting your phone will void your warranty.
Terminal Emulator for Android
Replace KingUser with SuperSU
MtkDroidTools v2.5.3-updated
adbd Insecure v2.00
SP Flash Tool
I am not going to get into how to install ADB drivers, MtkDroidTools, or SP Flash Tool. If you are not experienced with rooting, flashing, etc., please do some research.
Okay, let's get started
First you will need to get your phone rooted. Download KingRoot using the link above and follow this guide.
Next you will need to replace KingUser with SuperSU.
Now that we have the phone rooted and SuperSU in place, we can use MtkDroidTools to make a backup of the phone.
This video will show you how to backup your phone with MtkDroidTools (make sure you have downloaded the version I provided, as this has updated ADB files). Also make sure you enabled adbd Insecure before you connect your phone (you don't need to check enable at boot).
Once you have a successful backup, you need to create the files for flashing (scroll down to PREPARING EXTRACTED MTK ANDROID FLASH FILES FOR FLASH TOOLS) if you need to flash back to the original firmware.
Hopefully you now have a backup of your phone. Now we can install a custom recovery. You can use either TWRP (rename to recovery.img) or PhilZ.
The easiest way to flash the custom recovery is with SP Flash Tool. Connect your phone (you don't need adbd Insecure enabled for this). Run flash_tool.exe as administrator. For scatter-loading File click on the Scatter-loading folder
and navigate to your MtkDroidTools backups folder. There should be a folder that starts with BLU-STUDIO-C. Open that folder and select MT6582_Android_scatter.txt. For the recovery file, navigate to the one you downloaded (TWRP or PhilZ) by clicking on the Location column next to RECOVERY.
Make sure RECOVERY is the only box checked before proceeding. Now you have your scatter file and custom recovery loaded. Click on the Download button. Nothing will happen at this point. Now shut down your phone (not restart). Once your phone shuts down completely, plug it in via USB and you should see it begin to flash the custom recovery. If not, then you need to make sure you have the necessary drivers installed. Once it's complete, you can close out SP Flash Tool and disconnect your phone. After your phone is disconnected, hold down the power and volume up buttons until the recovery menu appears :good:
Post your feedback, and if you encounter any problems, please be as descriptive as possible. Good Luck
Credits:
@AlexZap who was the first to help me along this crazy journey
@yuweng for all his help in backing up the phone and for PhilZ recovery
@bigrammy for porting TWRP Recovery
@rua1 for MtkDroidTools
@carliv for CarlivTouchRecovery
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
cteeto said:
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
Click to expand...
Click to collapse
Glad it worked out for you. Yes, fastboot is also an option (as you all ready know).
Recovery could probably be flashed with Flashify, but haven't tried it. I am not a developer, so no I can't port any ROM's, and take no credit for the custom recoveries listed here.
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
sandix said:
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
Click to expand...
Click to collapse
ABSOLUTLY.......this would just be AMAZING...if anyone could manage to make a Cyanogenmod for this phone.....:good:
Bricked Blu Studio C (D830U)
Hey,
Was wondering if you could help me out here, as I'm a TOTAL Noob when it Comes to BLU phones But not to flashing....
I've Bricked by Phone, The Computer and SP Flash Tools still recognize the phone..
I've Downloaded the proper ROM from NeedRom.com....
My Issues:
1. Can you Verify WHICH Driver I should Be Using for a FULL either Erase/Download Or a Firmware Upgrade (Not Sure Which)
2. I need a Scatter File the Contains ALL the Memory address and Supplies ALL the Check Marks for a FULL Rewrite Flash....The One with the rom is missing Preloader Android, Cache, and usrdata...
When I did JUST the Scatter file flash attempt I got the BROM_ERROR : S_DL_GET_DRAM_SETTING_FAIL ( 5054 )
I googled that and it said the Perloader wsn't right So I added the Perloader (And checked the "firmware.info file" and seen the Memory:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
So I tried Anyway and got the same error except this time it's 4032.
So Basically Can you tell Me Which Files In the ROM I Download Go Into Which SLOTS on SPFTools, and Which memory address' are correct the firmware file or the Scatter??
I really don't want to keep slamming the phone with "STUFF" and REALLY screw something up, I think I'm lucky it's even being recognized at this point....
Also the MTK_Allinone_DA.bin that comes with SPFTools is the right one??!?!
I'm Using Version 5.13.52.200
I'm Assuming Just a FULL Scatter file would solve the problem?!?!?
ANYHELP In this Would be VERY much Appreciated....
Thanks
Mike
EDIT:
Ok, I got it to 4001 Error, And it's saying that error is it's not connecting with the preloader, So I'm thinking (hoping) if I can get those 3 files, even if the cache is empty as long as the memory address is right, and the scatter.txt, and do a Firmware upgrade, Hope, will solve the problem, if not, On to Test Pins...
@bobl61
Could work together to enhance MTKDroid liek as
Increae number of CPU recognize by it (ex. MT67xx - just recognize it - not work with it)
Update the apk included and sued by MTKDroid (like MobileUncle/Root Explorer/SuperSU)
Upload the ROM or the link I think I know what's the problem @Miker1029
Fixed from the dead!
Swaelae113 said:
Upload the ROM or the link I think I know what's the problem @Miker1029
Click to expand...
Click to collapse
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
IMEI Problem
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
Update, Just a Heads Up I'm Assuming from Googling around, that Installing the NVRAM will wipe your IMEI, Still working on this aspect, But it doesn't seem to be Hindering the phone in anyway, As I said It Took along time to boot up, So I'm not sure if Re-writing the NVRAM made it work or not, I do know I formatted + Download, and It Sat On the Splash Screen, I shut down and Flashed just the NVRAM file, and It booted.....
NOW Should I go for a Custom Recovery??? LOL.... I'll wait.... But now that I know I can Fix it......Hmmmmm
Mike
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
bobl61 said:
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
Click to expand...
Click to collapse
Hey Thanks, Maybe you can redo it or whatever, I was bricked for Months (Mainly Because i didn't know the Phone Type), Check out the screenshots to see the extent I went to Googling My Butt Off trying to figure it out, But once I did, All went good, I've flashed Atleast 100 Phones, For me, Friends, Family, Never had the Kind of issues I had with the MTK Chipset...
But now that I have it, It's rooted, Flashed, Xposed Framework Installed and working, Exactly what I was "Originally" trying to do....LOL, It's good now tho...
Now Funny thing I lost My Compass on it, and Sensor detector says it's working fine, So Not sure what's Interfering With it.... Hate to Re-Flash
SOOO, If I GOTTA re-flash Been looking around for 6.0 (Marshmallow) Build for it (No Luck)
1st Pic, Just the Face.
2nd Pic, Where I Cut the Battery Connector (Casing) to the Board so I could Disconnect the Battery without taking the phone apart....
3rd Pic, I left the screws out as There's a Little spring on the Bottom-Left (Looking from the back) that Makes the speaker work, And On the Bottom-Right is the antenna connection that I can't get to "Snap" back in..... So I left the screws out to fix those minor issues, I'm trying to NOT open it anymore then I already have LOL
Mike
I want custom ROM for blu studio c 5+5
[Q
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
bertucci25 said:
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
Click to expand...
Click to collapse
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Miker1029 said:
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Click to expand...
Click to collapse
Ok i'm going to explain my journey from soft-to-revive history:
I was trying to install a custom recovery for my D830U (Blu) and end up in this thread. I made all the steps
-Rooted the phone with kingroot
-Removed kingroot and installed SuperSU
-Instaled insecure adbd insecure
-I made a backup of my stock rom with MtkDroidsTool(wich is the needrom provided, since i flashed my phone while ago)
-Drivers are installed (VCOM)
Everything is downloaded from the links in the post
Ok at this point i did everything exactly like the guide, great
Ok now the part were "something" failed is:
I got the scatter file in the mtkdroidstool backup folder and REPLACED the recovery to the PhilZ recovery.img in the link of the first post. And flashed normaly. Here is where things got bad
I disconnected the phone and realized it got bootloop, couldnt start the phone and can't get into recovery (when i press vol+ button it goes to black screen), because i installed a bad/not compatible philz recovery.img(AGAIN ITS FROM THE PROVIDED LINK) ok now i'm worried but no problem, i tried to reflash with original stock rom and eventually after many tries i got into a normal recovery mode and the phone boots normal..
Now my phone is at the start point. Can you tell me which version of custom recovery are you currently using? Or what procedure should i follow to get into it? Again thanks! Cheers.
Ya I'll upload the recovery i used, I'll get it here sometime today..
I'm not sure which it is, as i said, the power connection for the battery broke off the board awhile ago, so it's either philz or twrp.
Also, if I'm remembering correctly, you have to add the other drivers, not the pre driver, you can try it with the pre, and if you don't get the green check use the other ones, and when you go flash, I'd backup your recovery you have now and put it somewhere safe...
Ill also add the version of xposed i used, if i can find it.. I know i had to install the. Zip files from recovery...
Mike
I believe this is the custom recovery i flashed, i no longer have the phone to test, but i believe i removed all except the stock and custom..
As i said back up your current recovery..
Let me know so i can mark it my puter.. Thanks
Mike
Also let me add, I had a bad philz also, not sure if i got it here, or somewhere else, but i have it marked as philz doesnt work on my computer...
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Miker1029 said:
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Click to expand...
Click to collapse
Hey mike im going to test this today i'll update my progress in a few! wish me good luck :silly:
Here's my understanding of getting custom ROMS for your device by doing little to no work.
If SHARP isn't releasing the source code, can't we just go and flash a ported ROM zip?
First, you find a device with exactly the same specs as yours: Easiest way to do this is googling phones with the same processor.
https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-400-msm8926
Now, we press "Compare" and see if we can find a phone that has exactly the same camera and/or other components.
Let's assume that our cameras are going to work out-of-the-box, and sort it down.
https://forum.xda-developers.com/leon
Oh, lookie! A phone with pretty much exactly the same specs, and a community that is making/porting ROMS for it?
https://forum.xda-developers.com/leon/development/aosp-5-1-1-lg-leon-ms345-t3611883
Hey, an Android 5.0 ROM?
Now, knowing the information we know now. Can't we logically go into the (aosp-5-1-1-lg-leon.zip) and change around the MANIFEST values to make sure they point to the correct places? Can't we change around the configuration so it will install?
I don't know all too much about porting ROMS, but if it's as truly as easy as I'm explaining it, why haven't we done it yet?
(Feel free to correct me if I have any details wrong! I'm open to criticism!)
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I am getting my sources from here: http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/OpenSourceCode.aspx
And compiling them using AnyKernel. I will post flashable ROM.zip here when I am done.
updates
Rhioun said:
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I will post flashable ROM.zip here when I am done.
Click to expand...
Click to collapse
any progress?
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
hi thanks for all very good news
can i flash with 305sh factory unlocked and rooted ?
No, that is a ROM for the 306SH.
The 305SH files are on a Japanese version of the Sharp website.. the links on these forums somewhere.
I can't test 305SH files, since I only own a 306SH.
If you could find the links for the 305SH system.img and boot.img, I could compile a flash able ROM for you.
Else, search around for a TWRP backup for the 305SH that you could restore on your phone.
Rhioun said:
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
Click to expand...
Click to collapse
Can you paste a few pictures? THX
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
A TWRP Backup is a nandroid backup, in essential, it took a backup of the whole partitions. The partitions include names that identify them, such as boot, recovery, cache, system, etc.
It is just asking you to restore what partitions you want from your nandroid backup.
Let's say, you updated to a new TWRP version, but it is buggy or something, and you wish to switch back. Simply click "Restore" and select only "recovery" and it should flash your nandroid backup of the recovery partition to your existing recovery partition, and you'll have your old TWRP again.
Since you messed a few things up already, I'd suggest you go with the full nandroid backup, leave everything selected, and click "Restore".
Hopefully you made the backup before you began fiddling too much with your phone!
Rhioun
Any progress at work?
I've tried porting multiple ROMs, looking for compatibility. I've had zero success in getting one to boot up. Either the device goes to a black screen after the primary Sharp Boot Logo, or it boots up TWRP immediately after the Sharp Logo.
I saw how another guy on these forums also made a flashable room for the Sharp Aquos Crystal using Superr's Android Kitchen, so I believe my next trial-and-error phase will lie there. However, before I do that, I plan to use his flashable ROM as a base to port other ROMs, and see if I have any more luck.
Maybe my flashable ROM was invalid somehow.
Anywho, I highly recommend anyone who's interested in porting ROMs for this phone to begin to do so. We have plenty of materials scattered about, and DuckDuckGo is your friend.
Don't hesitate to try.
Thanks, and I'll hopefully keep this thread updated about my progress.
I've working on an Android 5.1 RR ROM from the LG Leon. I've (so far) replaced a majority of firmware files and updated symlinks, dumped vendor files, replaced a few .ko files, edited the build.prop and updater-script, configured the fstab from the ramdisk, copied over the kernel built for the Sharp Aquos Crystal, and rebuilt the boot.img. I customized the updater-script to include chameleon.img, modem.img, and persist.img (partitions that assist with connecting to Sharp, and some kernel configurations).
This has been a lot of tweaking to the ROM, and I tested it and was thoroughly disappointed when my device began to bootloop. (Goes to Sharp 1st boot screen, and reboot, go to 1st boot screen, reboot, etc.). TWRP won't boot when this happens, and holding Volume Down+Power will yield nothing. You can't even power off the device, troubling because the battery is (nigh impossible to remove) not meant to be removed. No matter, although, holding Power Up+Power puts the device in fastboot more (the led will hold solid white) and from there you can successfully power off the device and start up TWRP. Luckily, I made a TWRP backup before I tried flashing the ROM, so I was able to restore back to that. However, I edited a good deal of things, so I just need to know what is causing the bootloop, or maybe then ROM, even ported, is simply incompatible with our Crystals.
I looked around, and found XDA Forums that promote the use of logcat to figure out why a device isn't booting. I am going to try this next, and if it yield nothing, I will find another phone to try porting a ROM from. (We have a good deal with the same processor, shouldn't be too hard.)
Sent from my Aquos Crystal
Still patiently waiting for a ROM. I'm still holding on to this device just because i have been watching this thread and i have hope it will have run custom ROM one day.
Geodripp said:
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
Click to expand...
Click to collapse
Sorry for my reply earlier, I skimmed your post and thought you were trying to RESTORE a backup since your phone was in such terrible condition.
Just to be clear, unless the 306SH gets a new recovery, there is usually no reason to backup "recovery" as that is just backing up your current TWRP.
(Usually used in case a new TWRP version is buggy and you want to restore back to your old one)
However, certainly backup boot as that contains all kernel files and ramdisk settings, and without it, the phone would not 'boot'.
Just backup everything. Leave everything checked. (Unless you're a stickler for space.)
I recently made a flashable Aquos Crystal Stock ROM (seems camera and data and everything work fine) with no carrier-specific apps installed.
I can supply you with that, or, if you'd prefer, I can make a TWRP backup of a factory default 306SH phone and send it your way,
for either of them, just put one on your SD Card and if TWRP Backup, press "restore" and select the backup I provided you with, or for flashable ROM, press "flash" and navigate to it.
There is really no difference between them.
However, some things to note if you do want me to supply you with a backup.
It has SUPERSU preset installed. (I can't change this. It made its way into about everything.) So, if you want to use apps like (Android Pay, Applike), you will have to open SuperSU, and click "UNRoot" and take it off.
I have fixed Kitkat 3rd Party SD Card write privileges, (bug in android 4), and that fix has also seemingly worked itself into my factory default as well. (No disadvantages to it, although..)
Both of these files will fix your issues and supply you with a factory default environment.
If you, or anyone else in this forum would like a factory default TWRP backup, or flashable zip, feel free to say so.
I'm at a standstill. I've gotten my hands on a niche version of CyanogenMod 11, and replacing some vital files, I got it to boot on Sharp Aquos Crystal.
However, files I replaced were apk's, system ui, libs, and breaks some (most) functionality of Cyan 11.
I need a boot log tool of sorts so I can replace files, do a boot log, figure out what is causing a boot loop, or forever boot, and fix it.
I looked online, and everyone is all about the logcat. However, I tried this and it says "waiting for device".
So the device does not reach booting adb daemon.
I need a tool that will save a boot log.txt to the SD card at boot, (I imagine init.rc ) so that I may debug the ROM and then use the working ROM (and logging tool) to port more recent ROMs.
Anyone know of any such logging facility/tool?
keep it up
Does anyone know of a boot debugging/logging tool? There must be one. Please reply to this forum or PM me about one, as I do need one.
It is vital to building a ROM, rather than stupidly copy-pasting and blind guessing playing at Roulette trying to get the ROM to work.
Please. I need one.