Related
Hi,
I'm relatively new at this, so please I apolgize if I make dumb questions and /or statements. I have a Wallaby that just won't get pass the boot screen. My screen has a white bacakground and has the following message:
"Welcome to
T-Mobile
G324e4
R6.25.02
4.01.16"
I have already tried flashing a cooked rom by using XDATools; however, I can't get the rom into the SD card. The OSImageTool.exe doesn't show my SD cards at all, so I can't dump the rom to the SD card.
I've also tried docking the unit, but it just won't sync with my pc.
It may be irrelevant, but I have the BootLoader 5.15 on my Wallaby.
I have read several posts regarding similar issues, but nothing I've seen has worked yet. I need some help sometime soon. Thanks
Have you tried using a card reader/writer on your pc for transferring rom image?
Yup.
Actually, my laptop has an integrated SD card reader on it (I am beginning to think this may be the real issue - compatibility, etc). Keep the suggestions coming though.
Thanks for the help, but... and still in trouble :?
Have aou tried another hard reset of the device? Maybe it helps to start the ROM....
Integrated SD-Card Reader / writer do make often problems with the XDA-Tools. Best (and i think only solution) would be buying an external Card-Reader/Writer (should be available for about 10 Euro...) or borrow one.
Then you're able ro reflash your device using a SD-Card.
2nd Chance you have is making an SD-Card dump of the OS of any other XDA. And then reflash your device with this Backup.....
I don't think there is any other possibility....
Stefan
LumpiStefan,
I did try hard resetting the device several times, but nothing happened. I will try to get another card reader and go about it that way.
By the way, I did think about getting the rom from someone else, but I don't know anyone in this city with an XDA.
All in all, thanks for confirming my theory of compatibility issues. I will give that a shot...
I'll write again to tell the story of the final outcome... "Will it live to see another day, receive another call? Or will it just become another victim lost in the valley of the Death?" :lol:
Stay tunned...
egsthunder1 and LumpiStefan,
I have this exact same problem. This phone sat on my desk for several months, I powered it up and charged it everyonce in a while. Now I wanted to give it to my daughter and it just sits trying to boot up. I let it charge for several day, soft and hard resets. I used the boot loader from a second device to dump its Tmobile official ROM to SD. I then Flashed the frozen device with the SD card. It was uploading for a while, said the flash was successful. I then did a hard reset and the same "welcome to Tmobile screen with G324e4, R6.25.02, 4.01.16. Both devices had a 6.22 bootloader.
Any help would be great. There was nothing done to this device other than sittng on a desk, draining to zero, charging and then a lockup.
Thanks for any and all help.
Paul.
Hey guys, I've been having this problems for years and I've been waiting for someone to find a solution but I guess no one has the answer. egsthunder1, what rom are you currently using? I'm guessing 2003? I suggest you re-flash your rom back to 2002, I think ROM Kitchen carries the 2002 one for the T-Mobile or whatever service you're using. Just cook the rom, download it, upload it into your SD card, and use the bootloader to download the rom from the SD. It works for me if you're willing to use your PPC again w/o 2003.
Back from the grave!!!
Well,
After seeing the light , my phone turned away from it and decided that it wanted to stay in the world of the living once more.
I was right in my assertions (and Lumpi verified that), the integrated card reader on my laptop was the reason why I couldn't flash the rom into an SD card. So I borrowed one from a friend, and presto!!!
My Wallaby now runs on 2002 since I cannot get 2003 SE (from the kitchen) to get past the boot screen, just like XDAPDA88 said it would. It was twice the work, but in the end it paid off.
I guess it is for the better since 2002 was far more stable than 2003 SE ever was (at least in my experience with the Wallaby). However, I now have a BA, and I couldn't be happier (at least until I get my hands on the Universal, then I will truly be happy
Thanks to all of you for your input.
Dear all,
I want to reverse the ROM from EXEC to ATOM.
I have the ROM image with me. Can anyone help me with the process?
Appreciate it very much.
Sorry for asking, what is your problem with your Exec ROM. Actually, I have also some issues re Exec ROM with my Atom and I would try to revert also tonight.
Actually, I have already reversed my Atom, because the ExtROM on my Not-Quite-The-Exec mysteriously disappeared for the 4th time so far this year.
(I should thank Quanta for giving us a buggy flasher, otherwise this procedure won't work, as the Exec bootloader specifically prevents flashing this way)
*DISCLAIMER: the following is my experience. I have no actual technical knowledge of the innards aside from anecdotal evidence. I take no responsibility for bricked devices. I am also not afilliated with O2, Quanta, HP or M$, because they have lately earned my utter disrespect.
*DISCLAIMER2: THIS IS ASSUMING YOU ARE USING A NORMAL ATOM. Not Life, not Stealth (that ain't no Atom), and not Exec. Just an Atom or an A-pure. I also have no idea what board version I have, but I do know it's one of the first releases of the device.
Here's what I did. I simply ran the Atom Exec DSUU (NOT the Atom one, the hacked Exec one you're probably using) all over again - on my device - while connected. If I'm reaaaal lucky, and I'm real lucky often, (especially if I leave my SIM in the device), I'll get a message "ExtROM Format Fail" right in the middle.
A reboot of the device at that point will render it in bootload mode, with just big text in the middle. IN THIS BOOTLOAD MODE, YOU CAN FLASH WITH ANYTHING, and the device won't complain AT ALL (At least that's what it seems). And yes, it connects via USB, and detects the USB connection. I don't think you even need Async running (hmm...some hidden USBHost functionality?), but I had mine in the background.
So I ran the original, unhacked 0426-mot0822 ROM upgrade - and it ran (it thought it was flashing into ROM version 0). In my case, it ended up not quite formatting the ExtROM correctly first time - because I didn't think my SIM was interfering with the ExtROM flash process until the third time. But I have my old ROM back now, 100% working - just keep trying the flash procedure again and again until the ExtROM finally goes through, and the rest of the stuff completes.
Hope it helps.
Ultimate Chicken said:
If I'm reaaaal lucky, and I'm real lucky often, (especially if I leave my SIM in the device), I'll get a message "ExtROM Format Fail" right in the middle.
Click to expand...
Click to collapse
I never experience this. Still, don't know how to revert back to Atom ROM.
Boatloader
I had the same problem but just entered boatlaoder and flashed the original ROM of Atom Pure, however, kept praying like hell till my Atom Pure rebooted with original ROM.
Knightro said:
Sorry for asking, what is your problem with your Exec ROM. Actually, I have also some issues re Exec ROM with my Atom and I would try to revert also tonight.
Click to expand...
Click to collapse
After changing to EXEC ROM, my Bluetooth cannot transfer files anymore.
Also, there are many other problems such as auto-rebooting and hanging at times of exchanging calls. Battery life drains out faster than normal. Basically the ROM is unstable.
Now, I previously read somewhere in this forum that we need to hold onto the camera button while hard-resetting the phone in order to get into bootloader and then dump the original ATOM ROM into the phone. But it didn't work when I tried it and now my phone's a little more screwed.
Did I get the procedure wrong? I couldn't find the old thread anymore, so hoping some bros out there can advise me what is the correct procedure.
Much appreciated.
tjkhattak61 said:
I had the same problem but just entered boatlaoder and flashed the original ROM of Atom Pure, however, kept praying like hell till my Atom Pure rebooted with original ROM.
Click to expand...
Click to collapse
Where can I find an original ROM of Atom Pure? Please help.
Jamez. I'm also experiencing hanging. Plus contrast problem and not charging on AC.
To others, what is really the difference in hardware between Atom and Atom Exec?
You can get the original ROM from O2's website.
I do have contrast problems but not the charging one.
Any bros out there to help us out???
Read this from other forum. Has anyone tried this procedure?
1.Before flash job done, backup all the things 1st
2.Then unplug the mini USB (must) and take off the memory card (it isn't matter)
3. Click the Camera button + reset button at the same time. U will see your Atom come to DSUU mode/Bootloader. it seem same interface as the command prompt at Win XP.
4. plug-in the Mini USB and can start flashing ROM.
(This method can flash to other language, but do it own risk, warrantly not covered)
Doesn't work!
Knightro said:
Read this from other forum. Has anyone tried this procedure?
1.Before flash job done, backup all the things 1st
2.Then unplug the mini USB (must) and take off the memory card (it isn't matter)
3. Click the Camera button + reset button at the same time. U will see your Atom come to DSUU mode/Bootloader. it seem same interface as the command prompt at Win XP.
4. plug-in the Mini USB and can start flashing ROM.
(This method can flash to other language, but do it own risk, warrantly not covered)
Click to expand...
Click to collapse
Thanks very much for the effort bro. It still doesn't work.
I followed exactly but after I tried to dump in the ROM, the bootloader shows "USB connection failed". This is getting frustrating!!!
my friend owns an 8525 and all of a sudden it stopped working (cant make/recieve calls and text messages). i tried doing a hard reset and it didnt work. he called att and the tech guy told him that his phone needs to reinstall the rom, which also didnt work. he bought a new phone and gave me the hermes so that i can play around with it. i tried installing wm6 on it and at 15% the update stopped.. and the phone reset itself. now.. it doesnt have a rom installed and keeps on going to the tricolor screen. i tried the unbrick method (in the wiki) several times and still no luck. it keeps telling me that i dont have enough ram but the booting still wont start. what are my other options for fixing this?... my kaiser was bricked before and i did the unbrick method for that and it work.. i havent tried that yet but is there any chance that it will work..?..
he doesnt need the phone anymore but hes hoping that itll be fixed so he can use it as a backup phone.. so.. yea.. any other ideas for ressurecting an old friend?
thanks!!
Sounds like the radio rom is dead.... Whats the SPL? You have a chance if it has Hard SPL installed - should say SPL - 2.10 olipro.
If so, try flashing a stock rom first, then a radio only rom. If you get no love, flash a cooked rom on it. I'd do it using the sd card method.
It should work as a PDA if you can't flash the radio, but its a brick cos no more phone calls...
If he doesn't want that, he could sell it on ebay for spare parts...
Cheers...
I just went through a similar situation last night. I am running dvh_79's v16 (build 19965.1.2.3) Lite. I added his HTC Today Plugin from the sdauto zip file but didn't like how the Today plugin slowed down my phone, so I uninstalled it and that's when my radio took a dump.
I used the instructions in the Hard SPL forum post #116 to unbrick it using the same rom and radio .nbh files and it went off without a hitch.
The first thing anyone should flash onto their phone is Hard SPL v7. Even before any skins. It won't make you 100% safe from bricks, but I'm damn glad I had it on there this morning while I was reinstalling my phone.
BTW ultramag69, I saw a lot of posts by you in various threads talking about unbricking a phone, and correct me if I am wrong, but if I have olipro 2.10 SPL on my phone (which I do), is it possible to initiate an install of a ROM image without being able to successfully boot the OS on the phone? Does Olipro automatically look for HERMIMG.nbh on the SD card? That was a point of confusion for me at first until I ran the HARDSPPL.exe file, but then again my phone didn't brick to the point I couldn't boot the OS.
What are the choices if you cannot boot OS? Are there any that can be performed from the bootloader itself?
Thanks.
well.. i did the kaiser unbrick procedure.. the mtty thingy.. it kinda worked. after that i installed the dopod wm6 rom... it handled the wm6 well---for a while.. after booting, the phone would turn off by itself (w/ 100% battery of course) or even restart itself..
sometimes it will stay on and be "fully functional" (w/o the calling and messaging still...) but somehow freezes when i look at the device information, specifically in the page where it displays the imei (which is missing btw...)..
the "phone" function doesnt work either, as it doesnt show the dialer.. and then after a few minutes, the phone finally freezes...
idk why this happens.. i tried installing other roms but the rom update always freezes. i tried 4 different roms already... so i had to do the mtty thing again...
(i have hardspl installed)
Codevyper, IF YOU HAVE hARD SPL INSTALLED, yes you can run the os flash. Just put the sd card in and reset. As the Hermes is going to the bootloader anyway it will recognise the flash file "hermimg.nbh". I've successfully fixed my phone when thats happened.
akosiryan, it sounds like you may have a corrupted radio rom. This is not gonna make you happy but this is ,at this point, almost 100% unbrickable. You could try to flash a radio only rom - no os, just the radio - but if it gets stuck and you've tried the stock rom then it looks like its a permanent brick...
You should be able to use as a PDA if you don't play with the phone functions though...
Just as a last shot, you could always use MTTY to check for bad blocks BUT this requires you to downgrade the SPL to 1.10 olipro to fix if you do. Please note though that sometimes the carrier does give you a couple of bad blocks to "brand" it as theirs...
Best of luck.
ultramag69 said:
Codevyper, IF YOU HAVE hARD SPL INSTALLED, yes you can run the os flash. Just put the sd card in and reset. As the Hermes is going to the bootloader anyway it will recognise the flash file "hermimg.nbh". I've successfully fixed my phone when thats happened.
Click to expand...
Click to collapse
Thanks ultramag69! I am indeed running olipro 2.10 on my phone so it makes me feel better knowing that if I can get the nbh on the card, then I can flash the ROM that way.
oh well.. me and my friend decided to sell his phone on ebay or sumthin..lol.. so its not a problem.. ill try to do one last step tho.. like flashing the radio only rom to see if itll work.. but i dont really care anymore.. lol.
No problem... If the Ebay from where you're from is like Aussie ebay, you should get approximately 1/2 to 2/3 the price that the working models go for. Generally the price goes up about 6 hours before the end of the auction with the price skyroketing in the last 10 mins... I'd probably give it a few days on Ebay to make sure people see it....
If you do get the radio rom working, Hermes (jasjam/dopod 838 pro) go for about $250 - $350Aud in Oz.
Cheers...
ok then! thanks
after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!
......
noone?????
The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)
Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...
Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .
i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck
There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL
It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?
another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL
When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.
I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.
The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!
Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.
It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.
Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."
The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!
Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.
I`m going to start cooking custom ROMs for my diamond and i don`t want to lose[/brick] it, i want it alive.
The question is, what actually bricks your device, a wrong cooked ROM or too many ROM flashes? Or both? I know that importing a ROM from another device to your kitchen and flash it to your device bricks it. Are there other ways to brick it?
My device has about 50 flashes and about 40-50% are with MTTY[/TASK 29]. How many ~ flashes can take a diamond before brick?
Sorry if my english is bad!
One has to establish what the term "bricking my device" is really intended to describe. Historically, it is used to describe when a device cannot be resurrected from a non-booting state and is generally non-responsive to attempts to get into bootloader. However, being able to get into bootloader doesn't necessarily mean that you'll be able to flash and recover, as I have seen two occasions where the person could get into bootloader, flash the appropriate stock rom and when the device reset, it simply returned to bootloader.
I go through all of this to contrast the above scenarion against what some folks have started to describe as "bricking my device" ... which is a bad flash, where the device doesn't get past the boot splash, but is easily resolved by going into the bootloader and flashing a rom that is known to be good.
Generally, the risk of really "bricking your device" is low as long as you are flashing SYS/XIP/OS only roms for your device.
Most folks get into trouble when the start messing with the boot loader and / or radio.
Based on MTBF, it has been stated that the average flash rom included in these phones could probably flash somewhere near 10,000 times.
All IMHO ... you'll do yourself a favor and, in addition to asking via this thread, use google to search for existing threads to get a variety of replies, just so you have visibility into the range of answers that you'll come across.
Best regards,
-boggsie
Thank you for your reply! I`ll search on google too.
I think that this question has found its answer.
Thanks again!
thecrazyman64 said:
I`m going to start cooking custom ROMs for my diamond and i don`t want to lose[/brick] it, i want it alive.
The question is, what actually bricks your device, a wrong cooked ROM or too many ROM flashes? Or both? I know that importing a ROM from another device to your kitchen and flash it to your device bricks it. Are there other ways to brick it?
My device has about 50 flashes and about 40-50% are with MTTY[/TASK 29]. How many ~ flashes can take a diamond before brick?
Sorry if my english is bad!
Click to expand...
Click to collapse
Okay, I learned it the hard way , cooking and flashing already costs me 2 devices.
The first device I only went back to my original rom when my devices acting weird, most of the time after 10 flashes, but after 6 months my device died.
My second device, I always flashed the original after a cooked build but that one only lived for 3 months.
So I decided to get myself another phone (all 3 phones are Niki btw) and only flash through sd-card, for now I already flashed my device 200 times without getting back to the original rom.
Regards,
Rataplan said:
Okay, I learned it the hard way , cooking and flashing already costs me 2 devices.
The first device I only went back to my original rom when my devices acting weird, most of the time after 10 flashes, but after 6 months my device died.
My second device, I always flashed the original after a cooked build but that one only lived for 3 months.
So I decided to get myself another phone (all 3 phones are Niki btw) and only flash through sd-card, for now I already flashed my device 200 times without getting back to the original rom.
Regards,
Click to expand...
Click to collapse
Well, this is why i got scared, the chef of the ROM i am using bricked his second diamond yesterday. And the second device lived only 1-2 months, but it was a used one.
I made only about 10 ROM flash in the normal way, RUU and USB cable, but now i am only flashing from internal storage and before that i use MTTY.