diamond bricked after flashing BELL UI beta 2 - Touch Diamond, MDA Compact IV ROM Development

Hello everybody,
I tried to flash my phone with the Bell UI beta 2 from here:
http://forum.xda-developers.com/showthread.php?t=445372
That didn't work because I got the error message INVALID MODEL ID, then I made a little bit of research and found this link: http://forum.xda-developers.com/showthread.php?t=409425 it explains how to bypass the INVALID MODEL ID problem, so I reconfigured the ROM and flashed it. Everything seemed to work fine when I flashed it, then after flashing I tried to boot the phone but it's stuck at the "touch diamond" startup screen. I'm able to get into the bootloader and I've already tried to hardreset multiple times with no success. I've got a DIAM100 with SPL-1.40.Olinex.
Now is there anyway of fixing this? Or do I have to send it in?
Looking forward to hearing from you,
Thanks!

not an expert on this, but just a couple things to note..
1) if you can enter bootloader, then you haven't bricked your device.. might want to change the post title..
2) have you tried flashing back to your stock ROM?

chriggi said:
Hello everybody,
I tried to flash my phone with the Bell UI beta 2 from here:
http://forum.xda-developers.com/showthread.php?t=445372
That didn't work because I got the error message INVALID MODEL ID, then I made a little bit of research and found this link: http://forum.xda-developers.com/showthread.php?t=409425 it explains how to bypass the INVALID MODEL ID problem, so I reconfigured the ROM and flashed it. Everything seemed to work fine when I flashed it, then after flashing I tried to boot the phone but it's stuck at the "touch diamond" startup screen. I'm able to get into the bootloader and I've already tried to hardreset multiple times with no success. I've got a DIAM100 with SPL-1.40.Olinex.
Now is there anyway of fixing this? Or do I have to send it in?
Looking forward to hearing from you,
Thanks!
Click to expand...
Click to collapse
Is it really bricked ?
ok try that :
Start your phone and maintain Vol Down,
you should enter in bootloader mode, so just try to flash with another rom.

chriggi said:
Hello everybody,
I tried to flash my phone with the Bell UI beta 2 from here:
http://forum.xda-developers.com/showthread.php?t=445372
That didn't work because I got the error message INVALID MODEL ID, then I made a little bit of research and found this link: http://forum.xda-developers.com/showthread.php?t=409425 it explains how to bypass the INVALID MODEL ID problem, so I reconfigured the ROM and flashed it. Everything seemed to work fine when I flashed it, then after flashing I tried to boot the phone but it's stuck at the "touch diamond" startup screen. I'm able to get into the bootloader and I've already tried to hardreset multiple times with no success. I've got a DIAM100 with SPL-1.40.Olinex.
Now is there anyway of fixing this? Or do I have to send it in?
Looking forward to hearing from you,
Thanks!
Click to expand...
Click to collapse
well any joy?

Since you can power on the device it is not really bricked I guess, cause last time I bricked mine, the power didn't even go on...
Guess you should just try another ROM

it's not as bad, as you think (hopefully):
-enter in bootloader mode (as suggested above)
-u'll see the colored screen with USB written on its lower side
- onnect it to your pc with USB cable
- start flashing a working rom in a normal way
it should work!

hey guys you are awesome! I didn't know that you can flash your device within the bootloader! I've now reflashed with a never bell version and it works great! Bell is really smooth TF3D could learn something from pointui ^^
Thanks alot!
Regards

I think we're done here!

Related

recovering the brick xda mini s

I tried to update the rom on my wizard, however it seems like I have basically messed it up beyond repair. I followed instruction to recover to factory default by pressing voice and comm button. I do get the screen where it says to press send in order to format. But, when I press send button -- the format fails. I have updated the rom by using CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe. It did update but wizard will not continue with boot process, it is stuck at the initial screen with ipl/spl screen
IPL 1.06
SPL 2.26
GSM -- I cant remember,
OS 1.5.x
Is there any way of recovering it -- or this is my brick for time being, until Linux is made to load on it? I would appreciate any help -- this is driving me crazy.
Thanks in advance.
Nick.
follow the instructions here,
http://forum.xda-developers.com/showthread.php?t=285435
also just try flashing you original rom again
if you have a boot screen, it's not a brick
nbhanji said:
I tried to update the rom on my wizard, however it seems like I have basically messed it up beyond repair. I followed instruction to recover to factory default by pressing voice and comm button. I do get the screen where it says to press send in order to format. But, when I press send button -- the format fails. I have updated the rom by using CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe. It did update but wizard will not continue with boot process, it is stuck at the initial screen with ipl/spl screen
IPL 1.06
SPL 2.26
GSM -- I cant remember,
OS 1.5.x
Is there any way of recovering it -- or this is my brick for time being, until Linux is made to load on it? I would appreciate any help -- this is driving me crazy.
Thanks in advance.
Nick.
Click to expand...
Click to collapse
Hiya.I don't know if it could work on an American Wizard.But I have a ROM that worked on mine.Mine was a o2 Mini s from the UK.If you manage to put it in bootload mode then there's a way out for it.
Just let me know if u can. My email: [email protected]
i have is xda o2 mini too -- I had bought it on ebay. please let me know how to solve that. when I try to format -- I get format failed. I am stuck now. it wont boot nor do anything
thanks
nbhanji said:
i have is xda o2 mini too -- I had bought it on ebay. please let me know how to solve that. when I try to format -- I get format failed. I am stuck now. it wont boot nor do anything
thanks
Click to expand...
Click to collapse
do you have an 'xda mini' or an 'xda mini S'?
o2 xda mini S -- similar to wizard or cingular 8125
if you can get into bootloader (hold camera button and use stylus to reset) you can flash the original rom from there
I dont have original rom saved. I bought the phone on ebay. I am able to update the roms -- but again it just hangs at the point of splash screen. problem began -- when I was using shelltool to upgrade to wm6 and my cell phone ran out of battery. I then tried to recover using formatting -- which it fails. I can update the roms -- from custom, to love to wm6 but it just hangs at the splash screen.
Logically it seems that it cannot find OS anymore. I get the blackscreen that has HTC logo on top left and diagnostics with oks on everything, then splash screen comes on and it just seats there.
any ideas -- I would be thank ful for that.
Nick.
if the battery is the problem, charge it outside of your wizard if possible.
are you cid unlocked?
is it g3 or g4?
what brand is your phone? try to download the rom from their website and flash that
I got another battery and got that working -- like I said, I can update the roms but it still hangs at the splash screen. it is g3 and according the to manual that came with it -- it is german model. I downloaded the rom from the o2 site and tried to apply that -- it fails with error # 300
quoting from the ruu read me file
"error [300]: invalid update tool
this error message will appear when you use the incorrect ruu version to upgrade"
are you CID unlocked? because it seems to me that, that is the reason

Can't flash anything after installing PDAVIET 2.07.06.PV

I've been using Mun_rus's WM6 ROM for quite a while and seeing that PDAVIET's rom was built on a more recent WM6 ROM I decided to flash PDAVIET 2.07.06.PV.
Since then I cannot flash anything on my Trinity, the update utility starts and when the progress bar reaches around 84% half the screen on the Trinity goes funny. The progress bar on the PC reaches the 100% (while the screen on the Trinity goes blank slowly slowly) but upon restarting the device PDAVIET ROM loads up again intact as if I have just done a soft reset!
I've even tried flashing WM5 again but without any success.
Trying to flash Hard-SPL does not work either and I'm running out of ideas now :-( Anyone else has this problem please? I would love to try flashing a ROM with an original IPL SPL but cannot find one. My bootloader currently says IPL 1.5/SPL 9.99.CP.
Yes I am having a similar problem. It starts to flash then stops reboots and on my pc says image fiile corrupted. I have re downloaded and extracted the files but it happens everytime. However. My trinity when it reboots is stuck in the splash screen.
I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.
i have the same problem...
i get 100% done and than it is still the old one..
Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now
deniser said:
Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now
Click to expand...
Click to collapse
I've run the splxploit a couple of times as well. It seems to finish the process succesfully but the problem persists :-( And mine is not stuck on splash screen, the device boots normally, it's just that whatever I flash does not work. Any more ideas please?
I tryed the all i think, read the all forum up and down, started in different ways, but no rom of SSL apply...
What is that!
I am stuck with this rom?
Any of the pro cookers can help with this please? I just need to understand what could be wrong, not necesseraly a solution
capeli said:
I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.
Click to expand...
Click to collapse
Hey many thanks Removing the miniSD solved my problem I flashed at least a 100 ROMS in my life and never bothered removing the memory card before ... but there you go
hi, i had the same problem. i flashed my trinity with original htc rom and after that when i tried to flash with any other rom it gave me success message after every try but in my phone there was still the same htc rom. i used that : http://forum.xda-developers.com/showthread.php?t=293632 AND IT WORKS. FROM THE MOMENT WHEN I USED THAT FILE I FLASHED MY TRINITY 2 TIMES WITH THE SAME ROMS WHICH DIDN`T WORKED PREVIOUS. you need to copy that file to your trinity and follow the instructions from the readme file. in my case i only opened it ,it started bootloader mode ,i disconected usb and connected it again and started ROMUpdateUtility with rom which i wanted.
interesting... so why does the miniSD card affect the flash?
kta- had you tried running sspl and then flashing during your failed attempts? (just curious)

Code corrupt!! help!!

My motorola defy keeps saying code corrupt, i tried to restore one of those 2.2 firmwares and then my phone kept restarting and wouldn't boot. So then i used rsd lite to flash with a 2.2 UK and 2.2 China. And they won't flash correctly. It keeps getting stuc kat like 9% or 13% executing. So now I have Code corrupt... Someone help me please! thanks in advance!
nvm. i got it to work, i flashed it with a small file first (boot_only.sbf) i got an error at first, but then redid the flash and it worked. idk why lol
could You tell me how exactly did You unbricked Your phone? I'm trying to flash boot only sbf (tried them all) but with no luck, I always get "error erasing subscriber unit". bootloader says "code corrupt"
I did a nice and clean upgrade by Higgsy's 2.2 minimal Chinese, it worked fine but it suddenly bricked itself.
Now I cant flash anything...
some advice anyone please?
doesnt help, but sry, no idea. :=/
good luck!
(but at least u know, someone's reading... and wants to help)

[Q] Soft bricked D855

Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
gavjs said:
Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
Click to expand...
Click to collapse
What is it that makes you say it has issues with the IMEI when flashing out of interest?
What the error with flash tool?
We can help you unless you get specific with the error messages dude.
Unbrick
gavjs said:
Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
Click to expand...
Click to collapse
Hi there,
I had the softbrick when I tried flashing the TWRP recovery image and screwed up. The phone didn't start up anymore and didn't go into recovery either. Just a black screen saying [680]fastboot. (on a D855).
Solution:
* Go to youtube,
* Type Unbrick LG G3,
* Open the video from ZEDOMAX,
* Follow the tutorial, all the links are in the description below.
With me, the first time I tried flashing the stock ROM it stoppedd at 15%, the seccond time at 94%, the third time it went all the way. Make sure wait long enough before you disconnect the USB cable. (The screen must be on 3!)
This should solve you problem.
Appologies for the weirdd description to get to the video. I'm new here so I can't popst direct links yet
WJ
Note 3 / SlimROM
LG G3 / StockROM
Hi
Many thanks for responding.
WJ - I was following a similar video but when I watched your suggestion, he made a bit of a deal about digging out an old windows laptop. I was using windows in VMWARE on my mac. I tried it using Boot Camp and it seems to have worked.
Cheers,
Gavin

[Q] Help! Fix Stuck on Boot Logo

Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.
riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode
riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.

Categories

Resources