hi
i have searched but couldnt find any answer .
i got dead xt910 , no chatging no led and on pc i get omap 4430 found.
i guess it bricked , but is there a way to wake it up ?
thx
trabel said:
hi
i have searched but couldnt find any answer .
i got dead xt910 , no chatging no led and on pc i get omap 4430 found.
i guess it bricked , but is there a way to wake it up ?
thx
Click to expand...
Click to collapse
i guess thats a nono ?
If you get OMAP4430 found (i.e NOT EVEN fastboot), then PM me.
xt910
I have the same problem, the device is determined for a few seconds as the "omap 4430" and disappears. Can you help me fix it?
helpful
do every thing told in this link
http://forum.xda-developers.com/showthread.php?t=2055839
amirali_b said:
do every thing told in this link
http://forum.xda-developers.com/showthread.php?t=2055839
Click to expand...
Click to collapse
With ubuntu can go to fastboot, somehow I see 1g size, but should be 16g
What i can do?
flash cdt failed =(
RiDER_RUS said:
With ubuntu can go to fastboot, somehow I see 1g size, but should be 16g
What i can do?
flash cdt failed =(
Click to expand...
Click to collapse
ok its have to flashable with RSD Lite now.
what is your phone model & last ROM installed on yore device?
you should flash your phone with fastboot file (do not update !! , just flash with last build which installed on your phone)
cdt.bin has some detail about emmc partition and start and end of them.SO you must have your Full flash fastboot file (i mean its format your internal memory too) and your fast boot must contain 'cdt.bin' (or 'cdt.bin_signed').
:good:
amirali_b said:
ok its have to flashable with RSD Lite now.
what is your phone model & last ROM installed on yore device?
you should flash your phone with fastboot file (do not update !! , just flash with last build which installed on your phone)
cdt.bin has some detail about emmc partition and start and end of them.SO you must have your Full flash fastboot file (i mean its format your internal memory too) and your fast boot must contain 'cdt.bin' (or 'cdt.bin_signed').
:good:
Click to expand...
Click to collapse
Motorola XT910, GB, Retail
Stock ROM android 2.3 before it bricks on update to android 4
I don't know what build it have
ok
Its not important whats your last build
just download a 4.0.4 GB retail fastboot and flash it on your phone with RSD lite and enjoy
amirali_b said:
Its not important whats your last build
just download a 4.0.4 GB retail fastboot and flash it on your phone with RSD lite and enjoy
Click to expand...
Click to collapse
xt910 is not defined in the windows as a device for RSD
!
even with fastboot mode connected?
Related
my friends,i have flashed a rom and dident boot and deleted the cwm.probably is for gsm or cdma and i dont now the way how to find it out my razr if it is cdma or gsm.well my problem is i cant find an official rom to flash with RSD lite,i am flasing from here http://forum.xda-developers.com/showthread.php?t=1362956 the xml file but rsd fails..what i must do?thank you for your time!
paris07121978 said:
my friends,i have flashed a rom and dident boot and deleted the cwm.probably is for gsm or cdma and i dont now the way how to find it out my razr if it is cdma or gsm.well my problem is i cant find an official rom to flash with RSD lite,i am flasing from here http://forum.xda-developers.com/showthread.php?t=1362956 the xml file but rsd fails..what i must do?thank you for your time!
Click to expand...
Click to collapse
need details ,which rom did you flash ? what is your model CDM or GSM etc.
Also, why does RSD Lite fail?
i dont now but i think a have gsm version because i flashed this rom before it brakes http://forum.xda-developers.com/showthread.php?t=1552166 and was working.After this,i dont remember which rom i flash and my phone braked.When my phone braked i tried all roms from here http://forum.xda-developers.com/showthread.php?t=1362956 flashed with RSDlite and all roms say fail in RSDlite(and all its so big rom 800mb?)what i am doing wrong?i bought it 3 days ago and i dont want to throw it to the garbage!!
paris07121978 said:
i dont now but i think a have gsm version because i flashed this rom before it brakes http://forum.xda-developers.com/showthread.php?t=1552166 and was working.After this,i dont remember which rom i flash and my phone braked.When my phone braked i tried all roms from here http://forum.xda-developers.com/showthread.php?t=1362956 flashed with RSDlite and all roms say fail in RSDlite(and all its so big rom 800mb?)what i am doing wrong?i bought it 3 days ago and i dont want to throw it to the garbage!!
Click to expand...
Click to collapse
When you downloaded the fastboot files and went to flash it in RSD Lite, did you extract the zip first? After you download the stock ROM you need to extract the zip file, then use RSD Lite to select the xml file and flash it.
Sent from my AXI0M ICS RAZR using tapatalk.
spc_hicks09 said:
When you downloaded the fastboot files and went to flash it in RSD Lite, did you extract the zip first? After you download the stock ROM you need to extract the zip file, then use RSD Lite to select the xml file and flash it.
Sent from my AXI0M ICS RAZR using tapatalk.
Click to expand...
Click to collapse
i did this steps
1 download drivers motorola
2 download rsd lite 5.6
3 download official rom
-
1 make sure drivers recongized my divice
2 extract rom and place it in new folder(rom incuds an ota file and many other like the xml)
3 when phone is close puse power button-volume down-volume up and select fastboot
4 connet to pc
5 open the rsd navigate to xml file puse start and fails
,,but what you mean downloaded the fastboot files?its already in the divice?
When youre in AP Fastboot Mode do you read Battery Low? If so, you have to get a Factory Cable or build one on your own. I did it otherwise, I removed my back cutted an old USB Cable and Connected the Red (+) and Black (-) cable directly to the Battery under the Backcover. Then I was able to Flash everything via Fastboot or RSD Lite.
So i have 4 XT910S phones. I wanted to put a EU or US firmware on them so they were no longer branded and didnt have all these apps on them.
So here is what I did.
downloaded 4.0.4 CN firmware (unbranded)
Rooted and backed up CDROM file and CID file
Flashed the CN firmware on the XT910S
Using the BT TOOLS trick it boots up fine
Flased CID.IMG through command prompt in windows
Now when it boots it goes straight to fastboot with the error
Invalid CG OTV (CG: cdrom): Invalid SP data
Invalid CG HAB (CG: cdrom, status: 0X0056)
Invalid CG OTV (CG: cdrom)
I tried restoring my original CDROM file but it says the image is larger than the partition.
the original backup CDROM file is 217,088 KB and the one that i am finding with EVERY other firmware is 216,832 KB
I have even tried getting backups of all the CDROM files off the other phones and they are all the same size
The original firmware is 67.42.17.xt910s.skt.en.kr but I cannot find it anywhere to download
HELP
your cid is no longer valid because cid version of xt910s 4.0.4 is 4 and the rom you installed has CID 5
now to bypass boot you will have to boot from bp tools or install boot menu manager after rooting, thats what i am doing
and to get throught that boot failure error
follow this
http://forum.xda-developers.com/showthread.php?p=43806194&nocache=1
thats how i recovered my xt910s
faheemakbar18 said:
your cid is no longer valid because cid version of xt910s 4.0.4 is 4 and the rom you installed has CID 5
now to bypass boot you will have to boot from bp tools or install boot menu manager after rooting, thats what i am doing
and to get throught that boot failure error
follow this
http://forum.xda-developers.com/showthread.php?p=43806194&nocache=1
thats how i recovered my xt910s
Click to expand...
Click to collapse
Thanks for the help. I have to ask if there is any way to get it back to normal? I need to sell these phones sadly, not for keeping and personal use. So is there any way to flash back to CID 4? I have experience with hex programming if that helps (I cannot see how C++ or pearl would do any good here).
N3401 said:
Thanks for the help. I have to ask if there is any way to get it back to normal? I need to sell these phones sadly, not for keeping and personal use. So is there any way to flash back to CID 4? I have experience with hex programming if that helps (I cannot see how C++ or pearl would do any good here).
Click to expand...
Click to collapse
Your CID isn´t changed and you can´t change it,each phone has its own CID.
Your CDT.bin was changed to 5,china boot and system are signed with secure version 5.
You shouldn´t restore your CID,because you flashed China kernel,then the phone can´t work.
Your option now is to flash EU JB with RSD Lite.Here https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip is RSD Lite 6.1.5 and here http://forum.xda-developers.com/showthread.php?t=2231289 are the JB Fastboot files.
still he need to root and install bmm otherwise his only option to boot is bp tools
welder73 said:
Your CID isn´t changed and you can´t change it,each phone has its own CID.
Your CDT.bin was changed to 5,china boot and system are signed with secure version 5.
You shouldn´t restore your CID,because you flashed China kernel,then the phone can´t work.
Your option now is to flash EU JB with RSD Lite.Here https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip is RSD Lite 6.1.5 and here http://forum.xda-developers.com/showthread.php?t=2231289 are the JB Fastboot files.
Click to expand...
Click to collapse
Sorry to ask just one more question. Will this get it back to normal without having to do any boot menu tricks or root? the phones are supposed to be sold and I need to make sure any idiot can use them. It is only 1 like this so if that one is a write off than so be it but just need to know.
N3401 said:
Sorry to ask just one more question. Will this get it back to normal without having to do any boot menu tricks or root? the phones are supposed to be sold and I need to make sure any idiot can use them. It is only 1 like this so if that one is a write off than so be it but just need to know.
Click to expand...
Click to collapse
I´m not sure,maybe you'll need to install BMM to boot normally.
razr xt910 problem, help required urgently.
Motorolla RAZR xt910s Problem
Dear All, I bought Motorolla RAZR xt910s a week ago. I tried installing Cyanogenmod 11 KitKat after rooting and installing CWM Recovery. Rom was successfully installed but the installation of G apps failed so i rebooted it.Now it shows the Motorolla logo screen and then goes black.Also i can enter the recovery menu by 3 key combination. i tried wiping data to factory settings and clearing cache but in vain. Today i tried flashing (using RSD Lite 5.6.4) a stock rom of ICS(4.0.4) and then JB (4.1.2) downloaded from a website but it shows error ''failed 6/12 flashing cdt.bin flash failed..............etc''. I have also tried using fast boot cable/factory cable but now it is giving the error of "read/write failed, unknown error" in moto fast boot and rsd lite software. How can i solve this problem of read write failed unknown error.
Please help on urgent basis... Waiting to hear from you people soon...
Have you tried matt's utility to restore stock ROM? See http://www.droidrzr.com/index.php/topic/764-gsm-xt910-razr-utility/
If successfully restored to stock then root using the utility, but do not install safe strap from the utility. You should then download and install the latest version of safestrap (version 3.65) and install it. See http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
I've read that only safestrap works correctly with cm11. So, now use safestrap to install cm11 (and gapps if you wish) in slot 2 (I've read that cm11 works best in slot 2).
Sent from my Droid RAZR Maxx (XT912, spyder) using TapaTalk.
mugheeshjaved said:
Motorolla RAZR xt910s Problem
Dear All, I bought Motorolla RAZR xt910s a week ago. I tried installing Cyanogenmod 11 KitKat after rooting and installing CWM Recovery. Rom was successfully installed but the installation of G apps failed so i rebooted it.Now it shows the Motorolla logo screen and then goes black.Also i can enter the recovery menu by 3 key combination. i tried wiping data to factory settings and clearing cache but in vain. Today i tried flashing (using RSD Lite 5.6.4) a stock rom of ICS(4.0.4) and then JB (4.1.2) downloaded from a website but it shows error ''failed 6/12 flashing cdt.bin flash failed..............etc''. I have also tried using fast boot cable/factory cable but now it is giving the error of "read/write failed, unknown error" in moto fast boot and rsd lite software. How can i solve this problem of read write failed unknown error.
Please help on urgent basis... Waiting to hear from you people soon...
Click to expand...
Click to collapse
follow the link i gave above in 2nd post
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
"The current image(boot/recovery) have been destroyed and can not boot.
Please flash the corret image"
Hey guys can someone help me ?
my device can't booting, because I patched my boot.img because I need to root it, and I don't have stock boot.img
Already downloaded from stock rom 4 times and corrupt
but I still can use the bootloader / fastboot
Maybe someone can help me with the boot.img ? I mean send/upload it
NB : I'm in .14 Rom
My device already unlocked/UBL
please someone help me with booting.img recovery.img
6 times downloaded firmware but I still got corrupted file
puttr said:
please someone help me with booting.img recovery.img
6 times downloaded firmware but I still got corrupted file
Click to expand...
Click to collapse
Bro, join telegram channel. you will get better support.
Telegram channel's full of impatient youth who are irreverent, arrogant and talk in pidgin English....If you fit the bill, you'll fit right in....
puttr said:
"The current image(boot/recovery) have been destroyed and can not boot.
Please flash the corret image"
Hey guys can someone help me ?
my device can't booting, because I patched my boot.img because I need to root it, and I don't have stock boot.img
Already downloaded from stock rom 4 times and corrupt
but I still can use the bootloader / fastboot
Maybe someone can help me with the boot.img ? I mean send/upload it
NB : I'm in .14 Rom
My device already unlocked/UBL
Click to expand...
Click to collapse
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Boot loop
AndriezSetyawan said:
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Click to expand...
Click to collapse
Im stuck at boot loop pls help
aslo give me the telegram link
Cookie Ninja said:
Telegram channel's full of impatient youth who are irreverent, arrogant and talk in pidgin English....If you fit the bill, you'll fit right in....
Click to expand...
Click to collapse
excuse me, wtf?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
malakaz27 said:
Im stuck at boot loop pls help
aslo give me the telegram link
Click to expand...
Click to collapse
may I know what you were doing before bootloop?
also feel free to join https://t.me/realme3pros
malakaz27 said:
Im stuck at boot loop pls help
aslo give me the telegram link
Click to expand...
Click to collapse
join this group https://t.me/r3pindonesia
your problem has fixed
same problem with me pls hlp
i got the same problem please heeeeeeeeeeeeeeelp i hope to fing solution quickly
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
well, but i dont know how to flash
venky34268 said:
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
Click to expand...
Click to collapse
i searched a lot and i ddnt find except one flash file .ofp and i dont know how to flash it ... pls tell me how to flash
Follow the guide only fastboot method.
nasser.56 said:
i searched a lot and i ddnt find except one flash file .ofp and i dont know how to flash it ... pls tell me how to flash
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-to-stock-rom-stock-recovery-t3940604
the files are there with the link
my phone is done
my phone is done :fingers-crossed:
i toke it to realme warranty and they flashed it
for free
they thought i flashed it with wrong way hahaha
Help me bro
harikp6247 said:
Bro, join telegram channel. you will get better support.
Click to expand...
Click to collapse
I aslo brick my phone
boot/recovery destroyed
give me link boot.img please bro
but how?
AndriezSetyawan said:
don't panic, it's pretty easy.
all you have to do is just install boot.img in the stock room. and the problem is fixed
Click to expand...
Click to collapse
#can you give tutorial, pls help me.
venky34268 said:
I have the same problem.i am going to flash all image files throuh fastboot.i will confirm here if it works
Click to expand...
Click to collapse
if you have the img files please share the link
Mod Edit: Every member is responsible for what they do with their device. Please be sure you know what you are doing, and that the method you want to use is correct for your device.
Guys finally I found the way to recover the device.
It should work on any real me device currently I am using real me 3 pro with color OS 6.0.1.
This is the solution for recovery/ boot destroyed message.
Here are the steps :
You are probably facing this issue because you have unlocked your bootloader.
First of all you have to lock bootloader of real me 3 pro using fastboot
Reboot your phone to bootloader mode
And connect to computer with USB.
here are the commands to lock the bootloader
fastboot oem lock
fastboot flashing lock -- this one I used
fastboot oem relock
( No need to use all you can try anyone of them )
Once you type this command in computer and hit enter it will ask to confirm the lock on phone
Use volume down keys for confirmation.
So here is the trick,
Color OS recovery is made to wipe the data whenever you lock / unlock bootloader.
So once you lock your bootloader on you real me 3 your color OS recovery will pop up ( even it is broke) for some seconds which will format your internal data.
Once you format the data your phone again will boot to recovery mode and same error will popup
" Boot / recovery has been destroyed "
Don't worry
Again power off the device wait for 10 seconds and reboot to bootloader mode not to recovery (very Imp) by pressing volume down + power key
Now you will boot in color OS recovery
( Note : if you didn't succeed try the above step 3-4 time because it took 3 attempt for me )
Surely you will boot in color OS recovery.
Now download the color OS OTA update file to your Memory card
( It is necessary to use SD card )
link :
https://www.realme.com/in/support/software-update
Download the latest firmware ozip file
Now create the folder in memory card and paste the firmware file over there
If you are already in color OS recovery don't reboot the phone just insert the SD card and select update. Select storage as
SD card
Select the folder and file and update.
It will take few minutes and you will be able to successfully boot in stock color OS ROM.
Enjoy.
You know the best part that I am writing this blog from the same phone only.
when i select the ozip file for update the processing stuck on 30%. thn faild
when i select the ozip file for update the processing stuck on 30%. thn failed
SharonBlack said:
when i select the ozip file for update the processing stuck on 30%. thn failed
Click to expand...
Click to collapse
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
different ozip installation also failed
hacker786 said:
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
Click to expand...
Click to collapse
flashable zip support stock recovery?? different ozip installation also failed .so plz help me
---------- Post added at 05:34 AM ---------- Previous post was at 05:01 AM ----------
hacker786 said:
Looks like the ozip file is not downloaded properly
Download the diffrent version and check
You can also try to flash the flashable zip from xda without bloat...
Click to expand...
Click to collapse
i also tried a14,a8 ozip stock rom.but after starting installation 2 minutes then failed
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
- I could flash in edl mode successful a stock firmware, but nothing changed after a reboot
- Device stays with "Hisense and powered by Android screen".
- The bootloader can't be unlocked
- teardown device and disabled battery for some minutes and tried to charge it with a wall charger -> bootloop
What I can (like before flashing in edl-mode):
- Entering edl-mode with a xiaomi edl-cable (Qualcomm HS-USB 9008er mode and diagnostic mode 900E after flashing)
- entering fastboot (pressing volume up while rebooting and connecting pc)
What I can't:
-flashing TF-Mode (Firmware on microSD)
-rebooting to system
-shutdown
-recharging wall charger (bootloop)
-not detected as usb-drive for filetransfer
This bootloop mode you can read quite often. The Xiaomi guys can fix this by flashing a fastboot Firmware, but they have an unlocked bootloader
Anybody knows a solution or what I can try to fix this?
Solved:
https://forum.xda-developers.com/showpost.php?p=82726877&postcount=7
JLowe said:
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
[...]
Anybody knows a solution or what I can try to fix this?
Click to expand...
Click to collapse
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
defylogic said:
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
Click to expand...
Click to collapse
Yes, sorry forgot that to mentioned. Good point. That was the first I tried with some other guys in the thread but it doesn't work at all. Tried different microSD and formatting.
Well if the TF Mode not working with 6.0.9 and you have 6.0.3 which is already rooted logic say to try not with 6.0.9 but with 6.0.4 update or better with 6.0.3 but original i.e not rooted. I think something in 6.0.3 is not compatiblle with something in 6.0.9. Simply as that. I remember I say guy in thread for Hisense A5 root which had all update files and WeChat group?
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
These are the original boot, recovery and vbmeta image from 6.09.06.
https://drive.google.com/file/d/1JeUEaBxpH5zu22v-6V_6LAqZzGuXmUhf/view?usp=sharing
Mehedi34 said:
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
Click to expand...
Click to collapse
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
lillo9546 said:
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
Click to expand...
Click to collapse
I'm sorry for asking what is probably a silly question, but how exactly do you flash files like boot.img using Qfil ?
I can get into fastboot., but not edl mode.
I know old thread, but am having problems with a bricked A5. After a lot of trial and error, it sometimes gets into Fastboot mode. I can then ask for fastboot device and it responds with a hex number and fastboot.
When I try to flashall new partitions, it fails with:
fastboot: error: ANDROID_PRODUCT_OUT not set or non allowed.
Once I could flash individual partition with:
fastboot flash boot boot_recovery_vbmeta_6.03.02/boot.img
Sending 'boot' (65536 KB) OKAY [ 2.113s]
Writing 'boot'
But then it just sits there and nothing seems to happen.
Anyone has suggestions on what to try, am running out of ideas
.
It would be amazing if anyone could share:
- Stock ROM 6.12 full QFIL backup.
- EFS/QCN backup files.
Thanks
JLowe said:
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
Click to expand...
Click to collapse
Hi. I have the same problem as you, but I don't know how to flash those files with qfil. Can you please explain it to me?