Related
Hi!
I tried to install Kitchen mod, and it went successful. But, then i tried to change the density in build.prop. Apparently something went wrong, and my phone froze at the load screen. So i went in to clockwork and did a recovery. But after that my phone booted into a very annoying bluescreen. I can't boot into clockwork, or anything. I can use the +/- to go into pink/purple screen.
Is it possible to fix this?
Greetings Arve
bluescreen... seems like the recovery.img is missing or corrupt. Try replacing it again
Hi again. I will try this once i get home. I figured out also that when i plug in the charger, it also goes into bluescreen Silly. But i will report back on how it works.
Thanks for quick reply
-Arve
Oh, snap. I opened the "removable disc f:\" And there was only(!) a folder called image, and a file called amss.mbn in it.
And then i copied over the original boot and recovery, but nothing happened.
Now i have no idea, bluescreen still comes =(
Thats no good, definitely sound like it got corrupted somehow..
There should be these files in the folder: (I can upload if you wish, but i'd recommend reinstalling a stock ROM and starting from the beginning because my image files are B137, although they're mostly the same)
amss.mbn
boot.img
EMMCBOOT.MBN
Recovery.img
Hi, that would be AWESOME! PM'd you =)
-Arve
install official rom,the problem will be solved
[email protected]@ said:
install official rom,the problem will be solved
Click to expand...
Click to collapse
Already solved
Just posting the fix here in case anybody would experience the same problem:
Oh, i put the missing file in first, and the bluescreen disappeared. But then i wouldn't get any further. Tried replacing everything and was then able to go into clockwork. Tried to recover the kitchen mod again, but didn't get further. Figured out that i wanted to try with the newest clockwork, so i installed the newest and tried the mod again. Voila Solved
arveparve said:
Just posting the fix here in case anybody would experience the same problem:
Oh, i put the missing file in first, and the bluescreen disappeared. But then i wouldn't get any further. Tried replacing everything and was then able to go into clockwork. Tried to recover the kitchen mod again, but didn't get further. Figured out that i wanted to try with the newest clockwork, so i installed the newest and tried the mod again. Voila Solved
Click to expand...
Click to collapse
HI there is it possible to PM me these files, I have done the same to my phone, and need them urgently
Thank you
akshizzle said:
HI there is it possible to PM me these files, I have done the same to my phone, and need them urgently
Thank you
Click to expand...
Click to collapse
There you go, it's not my own, but it should be fine >>http://dl.dropbox.com/u/13587974/boot.img_ORI_137SP04
In regards to recovery.img, just get this one, it's far superior to the original:
http://forum.xda-developers.com/showthread.php?p=14870348
katu2006 said:
There you go, it's not my own, but it should be fine >>http://dl.dropbox.com/u/13587974/boot.img_ORI_137SP04
In regards to recovery.img, just get this one, it's far superior to the original:
http://forum.xda-developers.com/showthread.php?p=14870348
Click to expand...
Click to collapse
IS there any way you could find amss.mbn or emmcboot.mbn?
I have totaly same but i cant get into recovery by any means. I've tried to restore files using my original boot files (made backup before any change) and i still cant get into clock, i just get blue screen any thing i do.
I'd really appriciate any help since im despert :// i have phone 4 days now
Can you issue adb commands? Logcat works?
u8800,cm7,[email protected]
help me u8800 blue screen
my u8800 get blue screen after format all things like image,cash.... by cwm
so i'm sooo sad my u8800 blue screen and i try to enter boot mode by keys up down and power pink screen appeared but no drivers install in pc
so i can't boot plz help
Pls help for blue screen
ryronz said:
bluescreen... seems like the recovery.img is missing or corrupt. Try replacing it again
Click to expand...
Click to collapse
Dear all i am very sad, i was using 2.3.5 official update on u8800 x5, then i tried to update 4.0, after installing that was not loading anything and got hang on startup,
then i tried to downgrade to 2.3 official cwm 5 was installed and i format everything, including boot etc, now it only shows blue screen. i can also go to pink screen, but as i connect to pc, it doesnt show and folder or drive so that i can copy dload or image files.
cannot access recovery mod or any type of drive during pink screen. how to solve my problem.
Remember i cannot access any drive or directory of device when connect to pc, no way to copy files or any thing.
arveparve said:
Just posting the fix here in case anybody would experience the same problem:
Oh, i put the missing file in first, and the bluescreen disappeared. But then i wouldn't get any further. Tried replacing everything and was then able to go into clockwork. Tried to recover the kitchen mod again, but didn't get further. Figured out that i wanted to try with the newest clockwork, so i installed the newest and tried the mod again. Voila Solved
Click to expand...
Click to collapse
could i have those files please the ones in the image folder i have a blue screen and its not cool!!!!
Yaar Please PM me the file.. I have the same issue.. thanks In adv..
ryronz said:
Thats no good, definitely sound like it got corrupted somehow..
There should be these files in the folder: (I can upload if you wish, but i'd recommend reinstalling a stock ROM and starting from the beginning because my image files are B137, although they're mostly the same)
amss.mbn
boot.img
EMMCBOOT.MBN
Recovery.img
Click to expand...
Click to collapse
---------- Post added at 12:48 PM ---------- Previous post was at 12:19 PM ----------
I'm also in the same problem. Please give a detailed description on what all are to do to fix this issue (blue screen on boot). I can see pink screen (vol + and -) and blue screen on boot. Please send the files and tell where to put those in..?
Please Help....:crying::crying::crying:
Plz Send Files to me also
ryronz said:
Thats no good, definitely sound like it got corrupted somehow..
There should be these files in the folder: (I can upload if you wish, but i'd recommend reinstalling a stock ROM and starting from the beginning because my image files are B137, although they're mostly the same)
amss.mbn
boot.img
EMMCBOOT.MBN
Recovery.img
Click to expand...
Click to collapse
Please send the files to me also. I'm also stuck in the same place.. Blue screen on boot!!! please give instructions for where to copy the files..?
mailtomeesubash said:
Please send the files to me also. I'm also stuck in the same place.. Blue screen on boot!!! please give instructions for where to copy the files..?
Click to expand...
Click to collapse
This is quite an old thread...try the other way he mentioned .
Sent from my U8800 using xda premium
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.
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
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
pikaetas said:
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
Click to expand...
Click to collapse
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Zeroemd said:
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Click to expand...
Click to collapse
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
pikaetas said:
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
Click to expand...
Click to collapse
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Zeroemd said:
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Click to expand...
Click to collapse
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
pikaetas said:
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
Click to expand...
Click to collapse
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
pikaetas said:
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
Click to expand...
Click to collapse
Well I am Glad your phone is alive !
anything you need PM me :good:
Ok guys bare with me. This is my first Thread. So it may look a little different then the others :laugh:
At least Your honor 7x will no longer be a paper weight
I posted last week that I do Indeed have a good TWRP Honor 7x BND-L24 USA Variant. Since then I have been getting hammered with requests for it. So being the great guy that I am, I have come to the rescue. NO MORE PAPER WEIGHT :laugh: I have also included TWRP 3.1.1. You will Find Direct download links below.
I have heard that Huawei will be releasing the firmware by end of next week. Go to play store and download Huawei Firmware
Finder(FF) To keep checking for it. Once there you can download it through Huawei FF.
When I did the backup TWRP gave me error 255 with the data.img but it did still back it up. I have the boot.img, system.img and data.img. data.img (data.img untested but should work)
If it does not I have a post here https://forum.xda-developers.com/showthread.php?p=75735265#post75735265 that explains how to use just the boot.img and system.img to recover your phone. IGNORE that it is for the 6x. It does indeed work with the 7x
If your phone is bricked and do not have twrp
1.Turn off phone
2. hold volume down while plugging in usb cable from your pc or laptop. That will put you in fastboot.
Tutorial here https://www.xda-developers.com/how-to-root-honor-7x/ on how to download and install ADB tools.
3.. Download TWRP 3.1.1 for honor 7x here https://drive.google.com/open?id=1dzP5ie7vQEn_dGfZHI383bt2sFxwtcTb
For people with TWRP installed
1. Download My TWRP backup here https://drive.google.com/open?id=1Udc4thELESZ4n_nXYmx6loQtTkjHOqSy
2. Extract the zip file to your ext, sdcard.
3. Boot phone into twrp.(Bricked phones hold volume up and press power to launch twrp assuming it is installed.
4. Select restore in twrp menu then choose sd card then the backup folder.
5. Flash the boot system and data img files
6 Reboot.
NO more paper weight :good:
Oh if anyone has twrp 3.2x that works with this with 7x BND-L24 do share please
Well hope this was not to bad :laugh:
Hit that thanks button. Yea that one under my post on the right :laugh:
Hope this has helped
Thank you
lowspeed said:
Thank you
Click to expand...
Click to collapse
No problem. Least I can do. This site has helped me out a lot
Paper weights suck :laugh:
Didn't work. I got to the "booting now" screen and was stuck there forever. I had to restore my old System and Boot partitions to get back to normal.
Didn't Work for me. goes tot the erecovery page.
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
tomjfmu said:
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
Click to expand...
Click to collapse
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
dukethedj said:
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
Click to expand...
Click to collapse
Yes please would love some insight on this. thanks in advance.
forgotenxlegacyx said:
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Click to expand...
Click to collapse
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
Would you mind linking a thread on how that is done? sorry for my ignorance
forgotenxlegacyx said:
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
Click to expand...
Click to collapse
i have an idea, maybe you can make a backup not just including the system, data, and boot but other stuff. Because I accidentally wiped everything, and I changed the vender to a10/tl10, and that bricked the phone even more. And the data img doesn't work. You can fix it with this https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468. If someone has a working bnd-l24 or bnd-l34 can you give me everything in the backup?
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
So you first do that then you do the rest?
Tried again. Getting the 255 error when flashing the Data
Yeah, error 255 is boot looping me too.
does it works well?
Thanks!
RoxRedEye said:
Thanks!
Click to expand...
Click to collapse
You were able to get it to work?
I want to get behind and support this, so much, .But the OP is not registered user, so cant even verify their reputation.
I am late to this device and thread, but my phone will arrive tmw.
I would like to know if this is the only current available restore method for BND-L24?