Unbrick way using raw flash image - Huawei Ideos X5 U8800

I tested an idea that i thought of (once seeing Modaco forum regarding using custom partition to increase program space) to the u8800 flash because I had three problems:
1- Lost 1gb from internal 2gb space using genko partition for 2systems.
2- Lost huawei logo (i got green screen with red and blue square).
3- Lost my IMEI as *#06# show 0.
First after booting in boot-loader mode (pink screen) I tried to repartition the internal space with the help of another u8800 standard phone (huawei original firmware) using EASEUS Partition Master 9.0.0 by reading and the original space then apply to my phone.. restart into boot-loader mode flash back the original firmware but updating never completes.
so, I thought of another idea which is copy raw image from the standard safe phone to mine (using winhex) & after search/replace the stored IMEI with mine (it was 22 occurrence).. what is the result..
It solved problems 1&2 but still 3 which is why my finding is half good. i tried to find another occurrence were IMEI is stored/encoded/reversed but no luck..
So before your phone is bricked please do raw image of your flash it'll save you many problems in one condition that is you phone can boot into boot-loader mode. The raw image is exactly 3,959,422,976 byte = around 4GB but once compressed with 7-zip i got it at 360MB

And how we do that?
Please, give some instructions

dancer_69 said:
And how we do that?
Please, give some instructions
Click to expand...
Click to collapse
which is your problem

Nothing for now, just I would like to have a raw image and a way to restore it in case that needed.

when you got that issue's?..1,2,or 3 month after use genko script?

I have used the script but i can not it was the cuase nevertheless take care by making the raw backup..

Related

[Q] U8800H - Not booting - No Recovery Mode - Only Bootloader Mode

Hello People,
Firstly I would like to apologize if this is a duplicate post, Googling reveals tons of different documents which actually has confused me and as I have tried many, I don't even know now what have I screwed up.
Phone - U8800H
OS - Linux
I tried to update my phone and it got messed up. It simply won't boot but go in an infinite loop or restarting every 3 seconds (once the HUAWEI logo is displayed).
By pressing both Vol buttons and starting the phone I can go into bootloader mode (pink screen) and the phone drives get mounted. However trying to go to recover mode by pressing the Vol UP key during start up simply again keeps restarting the phone.
I have tried various solutions which include re-downloading the images folder files again, replacing the recover.img from clockwork, formatting that partition and retrying, almost everything.
The phone simply keeps restarting. Replacing or removing any of the file in the images folder gives me a blue screen during going to bootloader mode.
As I cant get to recover mode I don't know what to do.
The warranty of the phone is finished as it was only of three months. I was told by the company I purchased it from to be a "power problem" but I think its a software problem as I messed it up myself.
If anyone has faced such situation before please help.
Thanks.
find original rom and reinstall it.
Otherwise what rom where you on?
arkudos said:
find original rom and reinstall it.
Otherwise what rom where you on?
Click to expand...
Click to collapse
U cant install rom without clockworkmod?
sent from ideos x5
eddydc1 said:
U cant install rom without clockworkmod?
sent from ideos x5
Click to expand...
Click to collapse
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
arkudos said:
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
Click to expand...
Click to collapse
Okk
sent from ideos x5
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
My guess is that some of the partitions got messed up somehow, some different filesystems (ext4 over ext3) in 2.3 stock fw.
Have you tried copying update.app to dload-folder of sdcard then booted phone with both vol-down and vol-up pressed (bootloader mode). That should in theory start the update...
Sent from my u8800 using XDA App
huzefa_from_kuwait said:
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
Click to expand...
Click to collapse
Ok then.... because I'm lost... which rom was on!
2.2.1?
or 2.3.?
these are the files needed FIRST....
---------- Post added at 05:31 PM ---------- Previous post was at 05:16 PM ----------
Ok IF you were on 2.2.... on sdcard make \dload folder with update 2.2 original rom!!!!
Vol+ Vol- Power on...pink screen and it should do the rest!!!
Recovery after you reinstall 2.2!
Now IF you managed to put 2.3... then put 2.3 update in sdcard \dload and again it should do the rest.
If you are trying to come back to 2.2 or miui oxygen cm7 from the beta.... first put the 2.3 beta back on via the sdcard.
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
huzefa_from_kuwait said:
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
Click to expand...
Click to collapse
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
julle131 said:
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
Click to expand...
Click to collapse
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
huzefa_from_kuwait said:
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
Click to expand...
Click to collapse
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
U8800
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
HFZenon said:
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
Click to expand...
Click to collapse
I have tried as you suggested, There were 5 partitions on the phone 2 of which were smaller than 200MB and therefore could not save the update file which is larger in size. I have tried over the remaining three partitions but in vain, they all end up with the same pink screen.
However you might be correct that my phone is not mounting the SD card as I can't see the SD card in the list of mounted drives in the computer.
To put/move files on SD card I have to use my another phone
I will get another SD card and try. In the meanwhile if there is anything else I could try, do advice me.
Thanks.
Nahkamies said:
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
I guess you got the same problem with sd-card not mounting properly if you can't initiate stock flashing via dload-folder-method.
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition. Then you'll hopefully be able to boot to recovery (vol-up + power), wipe data/cache/dalvik cache and flash whatever ROM you'd like. Remember this erases all your data, hopefully you've backed up whatever precious stuff you've got on your phone.
HFZenon said:
Hi, and welcome to XDA!
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition.
Click to expand...
Click to collapse
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Nahkamies said:
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Click to expand...
Click to collapse
Remember that you need all files from the same version. Try this, those are from stock 2.2 if I'm not mistaken. When (if?) you get into recovery, remember to clear cache / data / dalvik cache.
HFZenon said:
Remember that you need all files from the same version. Try....
Click to expand...
Click to collapse
Bingo! I'm very grateful of your help!
Nahkamies said:
Bingo! I'm very grateful of your help!
Click to expand...
Click to collapse
Glad to hear you get it working as we both had the basically same problem.
For me however still it is the same issue, except that while going into the recover mode now it shuts down instead or restarting endlessly. Where as the bootloader mode simply does nothing.
Can you post the exact steps you did to get your work so I can also repeat them?
Thanks.
@huzefa_from_kuwait:
You've got the U8800H right? Then you need to find the correct image-folder for your phone, as it differs from what I uploaded which is for U8800.

Unbrick U8800 with Odin?

Hi there!
I have bricked my phone and it is in "download" mode.
Is there a way to "bring it back" with Odin?
Thanks!
M.
Did they repaired your phone for the second time? If not, what did they said? What did you do in the first place that you bricked it?
Sent from my Ideos X5
Still waitin'
Nobody called me, don't know what's happening with my phone.
Get back here when new info available.
No, Odin is for Samsung
Better try to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1205307
darkfiremark said:
No, Odin is for Samsung
Better try to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1205307
Click to expand...
Click to collapse
People still doesn't read. I said that it is bricked! Cannot install anything on.
Brgds
What do you mean by download mode? if you turn it on with vol up and down and power held, what happens?
Try put stock rom (2.3 or 2.2 depending on what was on phone before) in dload folder on sd card and it might flash firmware off that.
If you're on download mode then you can upload a recovery an boot image. Do it and use that to flash any rom you want.
I appreciate people trying to help. But sometimes it is good to stay quiet. So please, don't reply with funny suggestions.
Thanks.
Hello;
What, exactly, is "download mode"?
For someone how's in need of help, you should take it easy on the atitude and provide more info for those sparing a moment of their lives to try to help you out, no?
bonowax said:
Hello;
What, exactly, is "download mode"?
Click to expand...
Click to collapse
http://androidforums.com/vibrant-tips-tricks/177526-how-enter-download-mode-what-worked-me.html
VuDuCuRSe said:
For someone how's in need of help, you should take it easy on the atitude and provide more info for those sparing a moment of their lives to try to help you out, no?
Click to expand...
Click to collapse
I am just trying to say that sometimes it is better to no reply at all.
If i said that the telephone is bricked and only in download mode you should know what does it mean before you reply. That's all. No hard feelings.
Try using a FAT32 formatted sdcard, with nothing in it but the dload folder with a stock ROM.
Couple days ago, I deleted all files from my U8800's FAT32 and EXT4 partitons - yes, even the 'image' folder, connected to my Linux box.
Because I wanted to revert to stock Froyo, i dumped back partition 5, from a backup I did some months ago - but this part is not relevant.
Formatted the card, dumped the dload folder into it, with a card reader; removed the battery and followed the procedure described in your link.
First try, it displayed some error message - can't remember - second try it showed up the pink screen, followed by the blue screen and initiated the ROM flashing. My phone is now fine and dandy... Oh, it rebooted three times after installing stock Froyo, so don't be alarmed when you get there.
Cheers
Good luck
bonowax said:
Try using a FAT32 formatted sdcard, with nothing in it but the dload folder with a stock ROM.
Couple days ago, I deleted all files from my U8800's FAT32 and EXT4 partitons - yes, even the 'image' folder, connected to my Linux box.
Because I wanted to revert to stock Froyo, i dumped back partition 5, from a backup I did some months ago - but this part is not relevant.
Formatted the card, dumped the dload folder into it, with a card reader; removed the battery and followed the procedure described in your link.
First try, it displayed some error message - can't remember - second try it showed up the pink screen, followed by the blue screen and initiated the ROM flashing. My phone is now fine and dandy... Oh, it rebooted three times after installing stock Froyo, so don't be alarmed when you get there.
Cheers
Good luck
Click to expand...
Click to collapse
I tried all you mentioned 30 X and more then that But no success
Btw: if you dumped back your partition from backup you had access to internal memory ... i don't have that connection neither on Ubuntu or Windows. I got pink screen but it is in "Download mode" only.
Thanks.
Can you explain me how did you get your Huawei u8800 enter in Download mode if it's a feature of some samsung smartphones to work with odin ?
You're being a little rude for those who're tryin' to help you, you should be more polite ma friend...
You didn't even say what rom were you using... so I guess you don't even deserve any help from anybody.
Peace
I've had download mode on my previous Android device - LG GT540. All it needed to enter such mode was to remove the battery, SIM and sdcard , and plug the USB cable. It would enter download mode and allow a stock ROM to be flashed with the standard LG update tool.
Actually, I dumped partition 5 back to the phone prior to erasing every file system in it, and indeed had pink screen mode access in order to do it...
Sorry it didn't work out for you.
Loureiro said:
Can you explain me how did you get your Huawei u8800 enter in Download mode if it's a feature of some samsung smartphones to work with odin ?
You're being a little rude for those who're tryin' to help you, you should be more polite ma friend...
You didn't even say what rom were you using... so I guess you don't even deserve any help from anybody.
Peace
Click to expand...
Click to collapse
I've installed some custom ROM and after reboot it stopped to boot in HUAWEI logo. And that was it. I have tried to install official ROM's all of them with standard methods (dload folder) but every time ends in step 2/2 (installation failed or something like that). I opened up new thread with that few weeks ago:
http://forum.xda-developers.com/showthread.php?t=1466953
This thread was supposed to answer my question at the top. And some guys did. I don't know how can thread be closed by the author. I've try to find it but with no success.
I appreciate people like to help. But if people don't know what i am asking why answering and asking questions that are answered in many threads before.
You see .. this thread should be as small as possible but ends with looong explanations which doesn't help at all
Peace.
Moved To Q&A​
We now have a Q&A section. Please post all questions there​

[Q] Nook Simple Touch Glow Light: Formated with MiniTool without Backup

Hi!
First at all, my apologies for my english erros, i´m from Brazil and I read in english much better than I wrote.
I rooted my Nook Simple Touch with Glowlight and when a I try unroot using a backup image (maded with Roadskil Disk Image) I realized the backup file have only 77mb. The problem is: I already formated all the partitions with "MiniTool Partition Wizard".
Then, when I turn on Nook, after the boot screen, shows this message: "Install Failed".
I already try:
-hard reset (power on + press left and right buttons)
-ClockworkMod + install factory.zip
I don´t know what alse to do...
Can anyone help me?
Thanks.
ummm .... dont worry ....i had same condition like u but fix , first .... burn ur uncompleted Image to ur nook and have a print screen to ur nook partitions via MiniTool Partition wizard ..... and then post here and remember dont delete ur uncompleted backup .... it's important and lets hope u have a luck with ur back up....
i will replay u between next Friday cuz busy in my exams
good luck
Hi speedman2202, thankyou for answering.
Now i´m working, tonitgh i´ll post the print screen.
But, I made some changes last night:
-Try to recover manualy the partitions (copying with Minitools).
-Sucefully recovered the "ROM" partition (NOOK partition was damaged).
-Hard Reset (8 boots), but nook wasn´t able to reinstall the stock rom.
Now my NSTG are stucked in "READ FOREVER" boot screen (but i can shutdown and reboot with noogie or ClockworkMod).
So, I´m begging to a charitable soul share with me a backup image of NSTG (could be without ROM partition, beacuse i´ve will use mine).
Thanks!
PS: Good luck in your exams.
ipedro3 said:
Hi speedman2202, thankyou for answering.
Now i´m working, tonitgh i´ll post the print screen.
But, I made some changes last night:
-Try to recover manualy the partitions (copying with Minitools).
-Sucefully recovered the "ROM" partition (NOOK partition was damaged).
-Hard Reset (8 boots), but nook wasn´t able to reinstall the stock rom.
Now my NSTG are stucked in "READ FOREVER" boot screen (but i can shutdown and reboot with noogie or ClockworkMod).
So, I´m begging to a charitable soul share with me a backup image of NSTG (could be without ROM partition, beacuse i´ve will use mine).
Thanks!
PS: Good luck in your exams.
Click to expand...
Click to collapse
the very important partition is Rom .... if it still fine .... copy all data from it to somewhere save on ur computer .... and then try get an Nook back up (NST or NST\wGL) they have same partitioning and then burn to ur nook when whn boot with noogie .... then empty all partitions from data (dont format just go to partition and del all files ) then copy ur Original rom files to Rom partition and as u have NSTw/GL then get the latest update from BN or the previous version and unpack them and repack them to Zipped or winrared file and boot with CWM image sd and then install the rar/zipped file ( as i remember zipped file is better) and then reboot ur device .... and should work fine
any misunderstand or problem replay me back .... ur nook cant be boot up successfully due to wrong partitioning ... so u need NST backup or get partitioning table for NST/WGL and partitioning with ADB tools .... Miss Renate did it for me once .... but i dont know how .... let me put u some useful links later
good luck
Thanks for your help speedman2202!
I´ve solved the problem using a stock image and overwriting the "rom" partition. Now works fine!
Here is a tutorial wroted by me to help others peoples: http://forum.xda-developers.com/showthread.php?t=2104145
Thanks again for you attention!
ipedro3 said:
Thanks for your help speedman2202!
I´ve solved the problem using a stock image and overwriting the "rom" partition. Now works fine!
Here is a tutorial wroted by me to help others peoples: http://forum.xda-developers.com/showthread.php?t=2104145
Thanks again for you attention!
Click to expand...
Click to collapse
nice Tut , i was about wrote it but i was busy ..... anyway nice u repair ur
nook again ..... TC about him and remember take backup again and make sure it's about 1.9 Gb ...... good luck
?
is there anything left to do if I dont have the rom either?
o6edd said:
is there anything left to do if I dont have the rom either?
Click to expand...
Click to collapse
i think , try search for recovery formatted files methods .... there's device can recover deleted and formatted partitions ..... try search for this services on internet ..... i dont know any other way till now
good luck
speedman2202, the first thing I do after the recovery was a backup...
o6edd, what you do with your nook??? try to describe for us.

[Q] Galaxy Young Startup with Red screen of death

Hi, i would like to find a way to fix a red screen problem.
A year ago i had a black screen and fixed it, used that solution for the red one but doesn't work.
Click to expand...
Click to collapse
When i start my galaxy young after the Galaxy Young GT-S5360 splash it turns into a red screen then shuts down.
Click to expand...
Click to collapse
I originally used Qualcomm NV Tools to read the SPC Code,
then i went into ADB shell & did su + setprop ril.MSL 123456, it worked fine, and the phone started good, but still no MSL / SPC Code, also used MSL Reader but didn't work. Also it didn't ask for root permissions.
Click to expand...
Click to collapse
Then here problems come. A red screen of death appears.
I tried using my USB Jig (even if download mode works without) to put the phone in download mode,
it worked, then connected to the computer using its original USB cable, before using Odin.
I though there could be a difference between "Factory" and "Odin" mode.
Used Odin version is 3.07 : The one that comes with "T Flash, Flash Lock, Nand Erase All".
Click to expand...
Click to collapse
I thought it was an efs problem. But how could i flash efs if totoro.pit comes with an EFS partition that doesn't have an img file? (the --11 Entry EFS without Image flash name).
I used PIT Magic (part of EFS Pro) to insert "efs.rfs" in Flash Name + FOTA, saved the file.
Click to expand...
Click to collapse
I checked re-partition and selected the totoro.pit file, i also've written "PhoneEnable=1" in Odin3.ini to use Phone Bootloader Update feature.
I inserted the Bootloader, PDA, Modem, & CSC Files. I checked Phone Bootloader Update.
The flash was fine, & efs.rfs (my most recent EFS backup image) flashed correctly into phone's.
Click to expand...
Click to collapse
But the phone still shows the red screen. I think the red screen is caused by "setprop ril.MSL 123456",
as i used qualcomm NV Tools many times and phone always worked fine.
Click to expand...
Click to collapse
The efs partition is usually not mountable in a galaxy y
Remove the sd card from your phone
Go into download mode
Flash the firmware from my firmware thread (links in my signature)
Never flash a pit file or bootloader - if you choose the wrong one you will brick your phone as you have discovered
If you can't successfully boot the phone after that you will have to flash the correct bootloader via a jtag - if you don't have one goto a repair shop as they cost about £200 UK pounds
If after that it still doesn't work might have to replace motherboard but you might as well put the money towards a new phone
Hi marcussmith2626,
I flashed Bootloader in the s5360 ODD package and used totoro.pit file
marcussmith2626 said:
If after that it still doesn't work might have to replace motherboard but you might as well put the money towards a new phone
Click to expand...
Click to collapse
Then i think it will be cheaper to buy a fresh new phone
Thank for your help anyway :good:
I fixed the problem 1 week after your reply, i could post solution if someone needs.
Killnolife said:
I fixed the problem 1 week after your reply, i could post solution if someone needs.
Click to expand...
Click to collapse
How you fix ?? i need so much !!! Please Help me ...
thiefxhunter said:
How you fix ?? i need so much !!! Please Help me ...
Click to expand...
Click to collapse
I took an hex editor and started the phone in download mode,
i took totoro.pit and added cal.bin under 'cal' partition name, and flashed custom pit.
(restarted and made a custom odin package with this cal.bin).
then i sent my latest cal backup (call this EFS Backup) and sent to device my cal.bin inside TAR file.
Then the phone restarted without problems.
Do you have an EFS (in fact cal) backup of your phone?
It's the bml15 block of your device. :good:
Killnolife said:
I took an hex editor and started the phone in download mode,
i took totoro.pit and added cal.bin under 'cal' partition name, and flashed custom pit.
(restarted and made a custom odin package with this cal.bin).
then i sent my latest cal backup (call this EFS Backup) and sent to device my cal.bin inside TAR file.
Then the phone restarted without problems.
Do you have an EFS (in fact cal) backup of your phone?
It's the bml15 block of your device. :good:
Click to expand...
Click to collapse
Can you upload the file?, this red screen of death is a common issue in the samsung galaxy young. thanks

My A120 Is Bricked very Hardly Plz Help Guyz!!!

Hello There!!
I was trying to get back to stock rom
And Always Getting this no space error 5069 While Flashing
After searching i found that format will fix this and i can flash like a charm
But after formatting my Device Is dead
no boot, no charging, no recovery
I'm Trying TO whole flash but I'm there is no option for that only Getting without bootloader one
Then i've checked it memory in memory test option now i'm getting
Nand Flash Not Detected
Plz!!! tell me what i can do to take my phone back to life
The Phone is out of warrenty
Same thing happend with me.
Use format+download all in SPFlashTool (with the same stock ROM), then do a firmware upgrade in SPFT with the same ROM.
Shahbaz23 said:
Use format+download all in SPFlashTool (with the same stock ROM), then do a firmware upgrade in SPFT with the same ROM.
Click to expand...
Click to collapse
Thanks for replying, i almost lost my hope of fixing this problem​
Now after trying it says:
1) after format+download it says no space error
2)then i tried firmware upgrade i'm getting " Failed to get PMT info " and "Invalid partition table" error in spft v3.xx
I've found many users are facing this problem, if it will fix here it will be great help for them
Just tell me what to do next​
lexileone said:
Thanks for replying, i almost lost my hope of fixing this problem​
Now after trying it says:
1) after format+download it says no space error
2)then i tried firmware upgrade i'm getting " Failed to get PMT info " and "Invalid partition table" error in spft v3.xx
I've found many users are facing this problem, if it will fix here it will be great help for them
Just tell me what to do next​
Click to expand...
Click to collapse
K, Try this for a change...
Assuming u already have all the required drivers installed (get it via google search, if not), use the latest sp flash tool (it does matter), browse your scatter file (i recommend u use the Stock JB/KK/LP) and goto the format tab (next to the download tab) and do an auto format. Now goto the download tab and do a format all+download and finally firmware upgrade (all this without the battery)... Now start your phone. This works fine for me when my phone get soft-bricked. However u must remember that formatting all may have risk of your NVRAM getting formatted and so loss of IMEI, but you can always have it fixed via AT command.
Shahbaz23 said:
K, Try this for a change...
Assuming u already have all the required drivers installed (get it via google search, if not), use the latest sp flash tool (it does matter), browse your scatter file (i recommend u use the Stock JB/KK/LP) and goto the format tab (next to the download tab) and do an auto format. Now goto the download tab and do a format all+download and finally firmware upgrade (all this without the battery)... Now start your phone. This works fine for me when my phone get soft-bricked. However u must remember that formatting all may have risk of your NVRAM getting formatted and so loss of IMEI, but you can always have it fixed via AT command.
Click to expand...
Click to collapse
Thanks for replying :cyclops:
I was using spft ver 5.1516.00
while auto format i was getting errors, in v5 it says BROM ERROR: S_DL_READ_PT_FAILE(5073), only v3.1328 can format it successfully while others v3 are getting invalid range error[I think this place will give some clue of what's happening]
ok then in format+download section( using spft V5)
format 100%
boot loader 100%
just after few seconds again no space error
Now in firm-upgrade section
again error failed to get pmt info
thanks for trying mate
now I have some hope for this device to be fixed
i'm not worrying about imei
anybody there plz bring my phone back to life
Help Guys I'm waiting for Ur Replies
PLzz!!
lexileone said:
Help Guys I'm waiting for Ur Replies
PLzz!!
Click to expand...
Click to collapse
Given your desperate condition, go with this:
Re-install the drivers and spftool from here: http://d-h.st/7CL
Use a different USB wire (maybe your I/O port of USB wire is damaged, happened with me once).
Then retry the method listed above of formatting, downloading and upgrading.
Hope this helps.
P.S.: I am not an expert so I couldn't understand the errors, but looks like these are common errors so you should get your phone back alive. :good:
Shahbaz23 said:
Given your desperate condition, go with this:
Re-install the drivers and spftool from here: http://d-h.st/7CL
Use a different USB wire (maybe your I/O port of USB wire is damaged, happened with me once).
Then retry the method listed above of formatting, downloading and upgrading.
Hope this helps.
P.S.: I am not an expert so I couldn't understand the errors, but looks like these are common errors so you should get your phone back alive. :good:
Click to expand...
Click to collapse
still getting invalid Pmt error on firm upgrade
and no space in download
plz help
Facing the exact same problem with my phone too.. Someone please help.
Is there any senior members who can help us?
Make full format (including calibration data & boot loader) then flash with jellybean
Auto format not make full format some data is not earse . make full format then flash with jellybeam stock rom
(Use latest sp flashtool
Without battery
Check Usb pin & cable are rightly connected )
Chinmayhegde said:
Auto format not make full format some data is not earse . make full format then flash with jellybeam stock rom
(Use latest sp flashtool
Without battery
Check Usb pin & cable are rightly connected )
Click to expand...
Click to collapse
But how
i can't see format with bootloader option in format tab
Is there Any other way to do this(may be manual format will work, but dont Know How to do)
This problem needs to be solved
Well thanks for trying
I hope we will get rid of this problem soon
lexileone said:
But how
i can't see format with bootloader option in format tab
Is there Any other way to do this(may be manual format will work, but dont Know How to do)
This problem needs to be solved
Well thanks for trying
I hope we will get rid of this problem soon
Click to expand...
Click to collapse
are you triad manual format including calibration data?
Chinmayhegde said:
are you triad manual format including calibration data?
Click to expand...
Click to collapse
Yes, the format was successful but still get same errors while downloading
PLz guyz Help !!!
lexileone said:
Yes, the format was successful but still get same errors while downloading
PLz guyz Help !!!
Click to expand...
Click to collapse
Change your stock rom for flashing kitkat or jellybean / wiko_rainbowlollipop official stock rom
use older spflash tool
then also u get same error service center is a batter option
Chinmayhegde said:
Change your stock rom for flashing kitkat or jellybean / wiko_rainbowlollipop official stock rom
use older spflash tool
then also u get same error service center is a batter option
Click to expand...
Click to collapse
In service center people are saying its board fault and it have to be replaced (pricing 3K)
But i'm sure the board is working
its any other problem
Have u tried both versions of sptools .format and download should work.try a different cable.if nothings working try adb from pc
micromax a120 1931 said:
Have u tried both versions of sptools .format and download should work.try a different cable.if nothings working try adb from pc
Click to expand...
Click to collapse
Thankz tell me more about adb from pc
lexileone said:
Thankz tell me more about adb from pc
Click to expand...
Click to collapse
1. Download SP flash tool (I think you already have) and Smartphone multiport download tool = http://www.mediafire.com/?1ycvu9ywv7vjnhv.
2. Open and run as admin - SPMultiPortFlashDownloadProject.
3. Click file, open download agent name' and add 'MTK_AllInOne_DA.bin'.
4. Open factory database and select the .mdb file.
5. Click scatter file - and select the .txt scatter file.
6. Then the 'top three boxes (LCD and camera driver) . You click last - ???????? button and unlock it for changing driver parameters.
7. Remember the 1st box for back camera, 2nd box for front camera, 3rd box for display driver.
8. My recommended :
under sensor 1 selectv5647_raw
under sensor 2 select:hi704_yuv
under sensor 3 select:T050UWV014NS or if it doesnt work LM050AMYBO1E
(if doesnt work change again and again)
9. Select high speed and no battery (I think no need to do).
10. Simply close the Tool. then open, SP flash tool
11. Select scatter loading, and load the same 'scatter file' , which you previously opened in the 'multiport download tool'
12. SELECT 'UBOOT' ONLY AND NOT SELECT OTHER ALL PARAMETERS. THEN CLICK DOWNOAD.
Then reboot your phone and check... display is ok ?
If not ok, Then again open smartphone multiport download tool and change the display driver and do the same all things previously.
You have to do repeatly, until, you are getting display normal.
The same thing for camera's working also. Do this ..I doubt adb will work just temme if it fixes it...

Categories

Resources