Database Users

Rogers Nandroid dump?

Is there anyone around with a Rogers HTC Dream?
if so, could you please do a nandroid backup of your phone and sent me the files?
I can't boot my phone after messing up reflashing it with incompatable firmware
Thanks in advance!

they are here

Yep they are there and I plan to leave them on that server permanently.

would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device

PurpleFries said:
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
Click to expand...
Click to collapse
yup fastboot.

k heres what i used
fastboot flash boot boot.img
fastboot flash system system.img
restarted and
still stuck on rogers screen
no change whatsoever

When I semi-bricked my phone these are the instructions I used.
Since you can get into fastboot you should be able to reload to factory settings no problem.
should be...
hmmmm, looks like you did the correct thing.
Just to let you know, after you reload the fresh copy of boot.img and system.img it will take much longer for your phone to turn on the first time, typically 5-10 minutes. It has to re-install the OS on the phone.

thats essentially what i did
however the link you gave me did not include a data.img
DISREGARD TEMPORARILY, waiting those 5-10 minutes
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well

PurpleFries said:
thats essentially what i did
however the link you gave me did not include a data.img
Click to expand...
Click to collapse
The data.img would be personal. It's not needed, but if you don't have when you flash your Dream it'll be like you're starting over for the first time.
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
Click to expand...
Click to collapse
AFAIK, the stock from is the system.img file. How lond did you leave it on the Rogers screen before you manually restarted your phone?

as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
EDIT
18 minutes so far...
not looking favorable T.T
EDIT2
yea its been 20 minutes, no change...
any other ideas?
EDIT3
30 minutes...
def not working

PurpleFries said:
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
Click to expand...
Click to collapse
yeah after 20 minutes it's certainly too long. I think mine only took about 5 minutes, but good luck. eeep
edit: worse comes to worse, take it back to the store and tell them your phone wont turn on.
Also you might be able to get more help tomorrow on the subject. I'm a fairly big newbie here so I don't know that much. There is a way for your computer to see at what point your phone may be frozen at but I can't remember how.
edit 2:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
That is from cyanogen, but it should give you some insight as to what your phone may be doing.

doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found

PurpleFries said:
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
I would just tell them I turned it on this morning and this happened. Ask them if they can fix it and see what happens. Mention nothing about trying to root it.
Just to make sure you're doing the steps correctly.
You're downloading the files I provided for you and placing them in your android/sdk..../tools folder right?
Then you boot the phone into fastboot?
Then I think you press the talk button to usb connect
from there you type in the commands.
Is that what you're doing?

exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device

PurpleFries said:
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
Click to expand...
Click to collapse
have you applied the update.zip file? Perhaps try applying that again first and then try the recover again.

which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?

PurpleFries said:
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
Click to expand...
Click to collapse
Well from that earlier psot I showed you that linked to HOFO step #1 had this.
Assuming you installed the update.zip before or after rooting (you can do it at any point really), now you can begin the recovery. First, enter the following into the command prompt
Click to expand...
Click to collapse
So it looks like the phone has to be rooted before you can apply the backup and to root the phone correctly you need the update.zip file.
The instructions to install the update.zip file and the file itself can be found here
Perhaps try to follow all of those steps, well skip the nandroid backup and see if your phone boots after that. If it does not but you can install the update.zip file then try the recovery method you have been trying.

tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working

PurpleFries said:
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
Click to expand...
Click to collapse
Sorry then. I'm out of ways to help. I don't really know all that much about the process. Perhaps your phone is slightly different than the rest of our Rogers phones so my backup files wont work on yours.
how long ago did you get it?

this thursday

[Recovery] Official CWM Recovery 5.0.2.6

I take no responsibility for any harm that comes to your phone as a result of applying this mod.
Official Clockwork Mod Recovery 5.0.2.6
Note that ROM manager support isn't currently complete. ROM downloads etc should all be working fine, but it needs to be updated to properly flash the recovery. At the moment it uses a method called fakeflash which will load the latest recovery from within whatever recovery you have installed. All other aspects are working fine though.
Download:
5.0.2.6: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.6-u8800.img
Installation Instructions (upgrading - root explorer method):
Using any file explorer which is able to remount as writeable (such as root explorer), browse to the /cust_backup directory and remount it as writeable
Navigate to the image directory and backup up the current recovery by renaming it to something like recovery.bak, or _recovery.img
Rename the downloaded recovery to recovery.img and copy to the image directory.
Installation Instructions (new install):
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Install any custom rom
Install rom manager and update to latest recovery
Source:
https://github.com/stockwell/android_device_huawei_u8800

That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?

You can't flash the boot images with cwm i thibk. Download and add this recovery img in /cust_backup/image folder its done.
And thanks stockwell. Haptic now work in recovery mode. Blue text version is much better than yellow
- U8800

blue text i like it.
thanks stockwell

stockwell said:
[*] Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups as it won't restore the cust image. If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Click to expand...
Click to collapse
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?

Thanks a lot . Good job.
Sent from my u8800 using XDA App

Druida69 said:
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?
Click to expand...
Click to collapse
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.

stockwell said:
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.
Click to expand...
Click to collapse
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.

Ok thank you stockwell, was just to have 200% sure

NForce25 said:
That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?
Click to expand...
Click to collapse
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
franciscofranco said:
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.
Click to expand...
Click to collapse
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.

This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...

Druida69 said:
This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...
Click to expand...
Click to collapse
its there to avoid mistakes i think
and to lead user to actually read whats written there

will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong

stockwell said:
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.
Click to expand...
Click to collapse
Thanks stockwell, will try later.

I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.

mesnati said:
I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.
Click to expand...
Click to collapse
What ?

stockwell said:
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself.
Basically the main hurdles preventing this previously were that we were reliant on using the init from the Huawei recovery, and also the offmode charge code was a direct modification to the recovery source. I spent quite a bit of time yesterday and today and have overcome these problems, and the result should hopefully be rom manager support in the near future.
What's different?
Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups made from an older recovery as it won't restore the cust image (its looking for boot now). If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Haptic feedback is enabled on touch keys, and the keypad backlight is turned on
When in offmode charging you need to pull the USB cable out and let it turn off before booting, you can't just press the power button to turn it on.
Backups are compressed
It's blue.
Download:
5.0.2.3: http://code.google.com/p/u8800-miui/downloads/detail?name=CWM Recovery 5.0.2.3-new_install.zip
Installation Instructions:
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Source:
https://github.com/stockwell/android_device_huawei_u8800
(Note that the device config isn't properly setup for anything other than the recovery, so don't expect to be able to use it for a fully working CM7 build)
Click to expand...
Click to collapse
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.

Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.

POST 1 today
"If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made."
For me is not pratical to change to 5.0.2.3. I have 12 Backups various. When I make a Restore I return to 4.0.1.5 and the renamed Recovery_backup.img on internal data storage are deleted. I continue whit 4.0.1.5.
Thanks.
........................................
EDIT: I made this and work (GENO method), no pink screen :
To install (you need root):
1. Backup /cust_backup/image/recovery.img
2. Download, extract and place the recovery.img into /cust_backup/image/
3. Done.
To go to recovery:
1. Power off
2. Hold Vol+ and Power buttons to power on (hold both buttons UNTIL you see the recovery)

HCDR.Jacob said:
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.
Click to expand...
Click to collapse
I changed it to /boot because first off I hate calling it /cust (it should be /cust_backup anyway), and second off because (unless I'm missing something, which I may well be) nandroid won't back it up without modification unless it's called boot. It doesn't **** anything up except for anykernel(which I fixed) because all of our rom install scripts explicitly mount mmcblk0p1 to /cust rather than just trying to mount cust and letting the fstab do the rest.
As for the rest of it, have a look at my github and my post. I'm not using the Huawei init and I'm not doing any modifications to the recovery source to achieve offmode charging. This port is fully functional and should be completely compatible with rom manager.
You're not obligated to do anything, I'm merely stating that ages ago you took money from people on this forum to buy a phone, and announced that you would be porting CM7 and getting official CWM recovery, so I expected rom manager support to come. Months later we have nothing, so I did it myself.
swayjd said:
Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.
Click to expand...
Click to collapse
There's no reason to change to this really, it's more of a 'pre-release' to make sure it works without any problems. If/when koush merges it into rom manager though this will be the version that's incorporated so I needed to make sure it didn't have any huge problems I missed.
Druida69 said:
will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong
Click to expand...
Click to collapse
His new version should work now, AnyKernel (the method used to flash the kernel to the phone) needed a small modification to make it compatible with new and old version of recovery.

[PATCH] Get back your PINK screen!

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.

[How To] Root - Backup - Custom Recovery - Blu Studio C (D830U)

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:

corrupted boot img(Qualcomm)[boost]

I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.

Thexmastermind said:
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Click to expand...
Click to collapse
Your not going to get a signal with Boost or any other CDMA carrier with custom ROMs right now. They work for GSM models but need to be fixed for CDMA.
Sent from my Moto E (4) using XDA Labs

Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.

Thexmastermind said:
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Click to expand...
Click to collapse
If you don't already have it, the Boost stock firmware is here: https://firmware.center/firmware/Motorola/Moto E4/Stock/
Download this one:
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
If you can't get RSDlite to recognize your device, you'll have to use adb/fastboot to flash the firmware manually piece by piece.
Sent from my Moto E (4) using XDA Labs

RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.

Thexmastermind said:
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Click to expand...
Click to collapse
I'm not sure what your problem could be other than not having the correct firmware. I haven't used RSD with this device (maybe someone who has will chime in) because it wouldn't recognize it so I've just been flashing it with fastboot on Windows with a script to flash everything automatically, so it's just as easy. It's the only time I really ever use Windows. You shouldn't need to erase anything before flashing. I've never had to. Be careful using the erase command, I've seen users screw up partitions using it and ending up with a brick. I only use it erase modem st1 and st2 and to wipe data.
Sent from my Moto E (4) using XDA Labs

I only have Linux ATM. My machine had XP on it till it crashed setting up eclipse lol rsd communicates with the device fine, so I'm assuming it's the firmware. Like I said I'm at family's for the holiday, but I'll keep you posted when I get home.

Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.

Thexmastermind said:
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Click to expand...
Click to collapse
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)

I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?

Quick question: when I flash twrp, leave it as read only, correct? Then flash verity, then su?

Thexmastermind said:
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Click to expand...
Click to collapse
No, don't leave it read only.

So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.

Thexmastermind said:
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Click to expand...
Click to collapse
Yes

Alright, so I got an error message about a bad key when I tried flashing twrp. I booted into twrp from fastboot via command line, flashed verity, flashed su "successfully" just waiting on partition details to be updated....
But it feels like it's been a good ten minutes of nothing happening. I ran the following from desktop:
adb shell whoami
Return was:
root
But I'm still waiting for it to update the partition details...

GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.

Thexmastermind said:
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Click to expand...
Click to collapse
You don't delete it. Be careful debloating.

Yeah I noticed there were a handful of apps that don't want be uninstalled. I saw a thread about it so I'll probably do a little more research.

how recovery?
pretty much same deal... how did you recovery to work