I need help. I locked the kaiser run Rom Original Pt in 15%, it locked with error264 ID SALESPERSON INVALID, now he doesn't leave the tricolor screen more, begin other Rom and the same thing.
Rom Version: 3.29.422.1 wwe
Rom Dates: 20/05/08
I radiate Verson: 1.65.20.29
S/N: HT822G002432
She long for has this Rom to try thank.
Thank you very much.
u didn't hardspl first did u? nor did u bother reading all the info this forum has, did u? if u search for kaiser stuck in tricolor screen (bootloader) u will come up with so many results as a post like this is made everyday !!!
now what u need to fix ur problem is either to flash oem original rom or post info from ur bootloader so it can be determined whether u have ruunbh errors or not.
thesire said:
u didn't hardspl first did u? nor did u bother reading all the info this forum has, did u? if u search for kaiser stuck in tricolor screen (bootloader) u will come up with so many results as a post like this is made everyday !!!
now what u need to fix ur problem is either to flash oem original rom or post info from ur bootloader so it can be determined whether u have ruunbh errors or not.
Click to expand...
Click to collapse
I began Rom Original pt, he didn't give right but it restarted, then I used JumSPL1.56 and it turned up to 15% and it locked.
My English is very weak, if it can help where I find this Rom, because I am trying but I don't find.
I would not like to give work, but II would not like to give work, but I am not any getting to solve. Thank you very much for the attention. am not any getting to resolve. Thank you very much for the attention.
Willgb said:
I began Rom Original pt, he didn't give right but it restarted, then I used JumSPL1.56 and it turned up to 15%....
Click to expand...
Click to collapse
Jumpspl is NOT FOR FLASHING roms ... it is strictly for flashing spls ... please please please do yourself the favor and read the wiki. I bet you now have ruunbh errors ... go to your bootloader and see if it says that:
to get bootloader, power down phone than power up while holding down the camera button.
thesire said:
Jumpspl is NOT FOR FLASHING roms ... it is strictly for flashing spls ... please please please do yourself the favor and read the wiki. I bet you now have ruunbh errors ... go to your bootloader and see if it says that:
to get bootloader, power down phone than power up while holding down the camera button.
Click to expand...
Click to collapse
He continues locked in this screen
Willgb said:
He continues locked in this screen
Click to expand...
Click to collapse
okay write down the information posted on that screen and post here... you might have to use a tool called mtty to fix your problem ... but lets me certain first.
thesire said:
okay write down the information posted on that screen and post here... you might have to use a tool called mtty to fix your problem ... but lets me certain first.
Click to expand...
Click to collapse
Good I call and he already appears in the tricolor screen, KAIS 100 SPL-3.29.000 CPLD-8, tried to run Radiate original 1.65.20.29 and it begins but it is locked in the 0%. If you need of more information it is only to say. Thank you for the help
Willgb said:
Good I call and he already appears in the tricolor screen, KAIS 100 SPL-3.29.000 CPLD-8, tried to run Radiate original 1.65.20.29 and it begins but it is locked in the 0%. If you need of more information it is only to say. Thank you for the help
Click to expand...
Click to collapse
okay i think you are just hung after a bad flash and you can use mtty to reboot the os here are the instructions on how to do it:
gsleon3 said:
Use of MTTY to recover from these errors is usually simple. The basic outline of how to use MTTY to resolve these errors is as follows:
1. Right click on the quicklaunch activesync icon on the lower left quadrant of your pc. (You can also just open up the A/S program)
2. Select Connection Settings.
3. Uncheck the box labeled "Allow USB Connections" & then Click "OK".
4. Open MTTY & select "USB from the Port options drop down menu.
5. Select RTS/CTS from the Flow Control Settings & click "OK"
6. Pay attention, because for a brief mmoment MTTY wil report whether or not it could establish a port connection to USB. If you are successful, a Command window will open.
7. Hit the "Enter" key on your PC twice. You should then see a command prompt that looks like this "cmd>".
8. At the command prompt (cmd>) you should enter the command "boot".
This will reboot the device & report back about any errors or bad or erased blocks.
9. If your device was just hung, it should be fine after the reboot. If it returns to Boot Loader however, it means there was a problem with bad blocks.
10. If errors were reported & you end up back at the Boot Loader screen, then repeat the "Boot" Comand at the (cmd>) prompt.
Click to expand...
Click to collapse
and here is the thread that has a link to download mtty.
Make sure you follow the directions to the T... do NOT miss anything... take each step seriously.
to get mtty:
http://forum.xda-developers.com/showthread.php?t=371154
thesire said:
okay i think you are just hung after a bad flash and you can use mtty to reboot the os here are the instructions on how to do it:
and here is the thread that has a link to download mtty.
Make sure you follow the directions to the T... do NOT miss anything... take each step seriously.
to get mtty:
http://forum.xda-developers.com/showthread.php?t=371154
Click to expand...
Click to collapse
The link of the files MTTY to see 1.16.zip and MTTY see 1.42.zip, they have problems you have another link. Thank you.
Willgb said:
The link of the files MTTY to see 1.16.zip and MTTY see 1.42.zip, they have problems you have another link. Thank you.
Click to expand...
Click to collapse
okay i don't know why you having issue make sure you are logged into xda before downloading ... here is the link for 1.42
thesire said:
okay i don't know why you having issue make sure you are logged into xda before downloading ... here is the link for 1.42
Click to expand...
Click to collapse
After I give enter, in the item 7, the mtty is locked. He doesn't answer.
Willgb said:
After I give enter, in the item 7, the mtty is locked. He doesn't answer.
Click to expand...
Click to collapse
I entered in Mtty, I proceeded until appearing cmd >, when I type boot, price Command error!!!.
What to do of here for front?
Willgb said:
I entered in Mtty, I proceeded until appearing cmd >, when I type boot, price Command error!!!.
What to do of here for front?
Click to expand...
Click to collapse
make sure there are no spaces ... otherwise it won't work.
thesire said:
make sure there are no spaces ... otherwise it won't work.
Click to expand...
Click to collapse
I typed without spaces and the same thing happened.
Willgb said:
I typed without spaces and the same thing happened.
Click to expand...
Click to collapse
sigh... you ask for help in private message but even for just this simple instructions given by thesire and you can't follow! You shouldn't even tried to flash a ROM!! Try to work this out first because if you can't, no offense bro but I hope you still have warranty on your Kaiser
pfcsabre said:
sigh... you ask for help in private message but even for just this simple instructions given by thesire and you can't follow! You shouldn't even tried to flash a ROM!! Try to work this out first because if you can't, no offense bro but I hope you still have warranty on your Kaiser
Click to expand...
Click to collapse
The whole commands that were passed already executed and I didn't get progress, the problem is that wandered of program in the hour of updating and I also lost already the warranty. For the that I researched I need Rom Original ROM 3.29.422.1 Radiate 1.65.20.29. If it can help me, I thank. Thank you
Tilt Bricked
pfcsabre said:
sigh... you ask for help in private message but even for just this simple instructions given by thesire and you can't follow! You shouldn't even tried to flash a ROM!! Try to work this out first because if you can't, no offense bro but I hope you still have warranty on your Kaiser
Click to expand...
Click to collapse
I already tried to turn countless Roms and appears error 264. It is for this reason that I sent msg for you in the hope that you can help.
Thank you and excuse if I inconvenienced.
Related
I have the new Hard SPL installed and when I try to install the Dutty 1.1 it's reseting my device and show likes it going to update and it just sits there at 0%. After that it says stuff about recovery and I do all that, and get everything back to normal again. Last I try the update agian and stuff get the same thing over and over.
Has NE1 ran into this problem at all?
I had the same due the fact that I had not run hardspl before installing the ROM.
A matter of "READ THE MANUAL"!
did u get it fixed? i installed the hard spl thou..
Also I tried installing a different one now and I get the same problem?? what is going on?
masta7100 said:
did u get it fixed? i installed the hard spl thou..
Also I tried installing a different one now and I get the same problem?? what is going on?
Click to expand...
Click to collapse
I got it working now.. i feel like an idiot
masta7100 said:
I got it working now.. i feel like an idiot
Click to expand...
Click to collapse
I felt the same.
The good thing is that you fixed it!
robix said:
I had the same due the fact that I had not run hardspl before installing the ROM.
A matter of "READ THE MANUAL"!
Click to expand...
Click to collapse
As my dad always told me.
RTFM (Read the f*%$#[email protected] Manual)
Can you guys tell me which version of hardSPL you used? When i try using kaiser-HardSPLv1 and also Kiaser-HardSPL-3.28 and both fail to install. Where am i going wrong?? Thanks in advance for anyone's assistance.
_____________
ATT Tilt
GSM... Unlocked
KAIS1*0
SPL-3.56.000
CPLD-8
WM 6.1(CE OS 5.2.19214)
ROM:3.57.502.2 WWE
Radio:1.65.21.18
givantake said:
Can you guys tell me which version of hardSPL you used? When i try using kaiser-HardSPLv1 and also Kiaser-HardSPL-3.28 and both fail to install. Where am i going wrong?? Thanks in advance for anyone's assistance.
_____________
ATT Tilt
GSM... Unlocked
KAIS1*0
SPL-3.56.000
CPLD-8
WM 6.1(CE OS 5.2.19214)
ROM:3.57.502.2 WWE
Radio:1.65.21.18
Click to expand...
Click to collapse
Install hard SPL 3.* exactly as in post #2 of this thread: http://forum.xda-developers.com/showthread.php?t=396922
If the first method doesn't work, try the second one.
Thanks
Dave
such a dunce i am
thank you SIR, soo kind, soo kind! i could kick myself in the tosh for not reading through the instructions. Thanks again!
Kaiser 100 (TILT 8925) during Flashing, the battery was discharged. Now it does not join, the green light diode only burns at power ON attempt.
The computer defines it on USB as Flash device, but the driver from ActiveSynch do not approach.
How to restore it ?
What buttons for input in Flash mode (tricolor) ?
BR !
This is in the wrong section of the Kaiser.
Anyhow, enter bootloader mode by fully pressing the camera button and doing a soft reset simeltaneously. Once you're there, flash a ROM.
kareem9nba said:
This is in the wrong section of the Kaiser.
Click to expand...
Click to collapse
Sorry.
Mod's remove my topic to right place, please.
kareem9nba said:
Anyhow, enter bootloader mode by fully pressing the camera button and doing a soft reset simeltaneously. Once you're there, flash a ROM.
Click to expand...
Click to collapse
This combination don't work for me.
Any other idea's, please.
BR !
It should work; you're just probably not doing it correctly. Make sure to have the camera button completely pressed and stylus in the reset whole for a few seconds until you get the tri-colored screen.
kareem9nba said:
It should work; you're just probably not doing it correctly. Make sure to have the camera button completely pressed and stylus in the reset whole for a few seconds until you get the tri-colored screen.
Click to expand...
Click to collapse
I did exactly as You wrote up.
I push camera button completely pressed and stylus in the reset whole for a few seconds
But, PC recognize it as Flash Device, and noone from ActiveSynch driver's does not approach for this mode.
Tricolor screen also not appear.
eh, probably you have no SPL now...
install the Qualcomm drivers: http://forum.xda-developers.com/attachment.php?attachmentid=71038&d=1203255530
does that go OK?
cmonex
Thank You !
Will try.
WBR !
cmonex said:
eh, probably you have no SPL now...
install the Qualcomm drivers: http://forum.xda-developers.com/attachment.php?attachmentid=71038&d=1203255530
does that go OK?
Click to expand...
Click to collapse
Yes, I installed Qualcomm drivers, and driver's is OK, thank You for driver's.
But what I must do now ?
How and what SPL I need write there ?
WBR !
I think you need to use the FrankenKaiser SPL Loader...
But I am not 100%.
Ta
Dave
DaveShaw said:
I think you need to use the FrankenKaiser SPL Loader...
But I am not 100%.
Ta
Dave
Click to expand...
Click to collapse
From where I can get it ?
WBR !
er1cc said:
From where I can get it ?
WBR !
Click to expand...
Click to collapse
Ok, your humble servant quit the job.
Now you must use the search button.
er1cc said:
From where I can get it ?
WBR !
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=394584
It says you need a security unlocked device. Do you know if you have done this?
If not, I'd wait for cmonex to have a look. I'm a novice at this
Dave
DaveShaw said:
Here: http://forum.xda-developers.com/showthread.php?t=394584
It says you need a security unlocked device. Do you know if you have done this?
If not, I'd wait for cmonex to have a look. I'm a novice at this
Dave
Click to expand...
Click to collapse
Yes !
Thank You, DaveShaw !
It is what I need.
But when I run FrankenKaiser-SPL-Loader.exe , WindowsXP closed DOS window with error.
What is wrong ?
I think better I need wait for mr. cmonex, for his answer about that.
WBR !
er1cc said:
Yes !
Thank You, DaveShaw !
It is what I need.
But when I run FrankenKaiser-SPL-Loader.exe , WindowsXP closed DOS window with error.
What is wrong ?
I think better I need wait for mr. cmonex, for his answer about that.
WBR !
Click to expand...
Click to collapse
I think that's best, but mr cmonex doesn't exists, mrs comnex on the other hand...
DaveShaw said:
......doesn't exists, mrs comnex on the other hand...
Click to expand...
Click to collapse
I wait.
WBR !
er1cc said:
Yes !
Thank You, DaveShaw !
It is what I need.
But when I run FrankenKaiser-SPL-Loader.exe , WindowsXP closed DOS window with error.
What is wrong ?
I think better I need wait for mr. cmonex, for his answer about that.
WBR !
Click to expand...
Click to collapse
what was the error?
and are you security unlocked at all?
also we better know your exact radio version because the described step 6 in that thread can differ (the exact command might need a different number to be typed). do you know the radio version?
if you answer with no to either of the last two questions, contact me in PM and we can look at it in more detail.
DaveShaw said:
I think that's best, but mr cmonex doesn't exists, mrs comnex on the other hand...
Click to expand...
Click to collapse
not mrs yet, no
I thought you get to the tri-colored screen by holding down both the camera button AND the power button, and then do a soft reset?
biscuits1978 said:
I thought you get to the tri-colored screen by holding down both the camera button AND the power button, and then do a soft reset?
Click to expand...
Click to collapse
no, power is not needed.
the way to do it:
hold camera, press reset (don't hold reset, just press it once), release reset, keep camera held for like 5 seconds then release it.
cmonex said:
not mrs yet, no
Click to expand...
Click to collapse
well definitely not mr.
Dave
5.05A
Just Download Elf.zip for ELFIN Service manual.pdf, u'll know how to use it.
911sniper said:
2008/08/18 Release V5.05A for ASP
Click to expand...
Click to collapse
Holy crap!
Thanks! now let's see if this helps with Gold Card users not being able to unbrick.
can u plz explain me what this actually is? am guessing its a diagnostic utility for the elf but how and when are we supposed to use it?
xmodinc said:
can u plz explain me what this actually is? am guessing its a diagnostic utility for the elf but how and when are we supposed to use it?
Click to expand...
Click to collapse
There's some information in the Herald Goldcard page (check the link from the Elfin Goldcard wiki).
I haven't tried it yet.. but maybe it does some cool stuff like bypassing Model ID check?
Are you able to get the SDO file as mentioned in the service manual (page 35)? I assume this is an all-Elf unbricking image.
The HTC website requires login to obtain it.
dsixda said:
Are you able to get the SDO file as mentioned in the service manual (page 35)? I assume this is an all-Elf unbricking image.
The HTC website requires login to obtain it.
Click to expand...
Click to collapse
Can't help for that...
Hi!
I test the file on my bricked Elfin.
Normal flashing via SD card is impossible because the bootloader doesn't start the flash process.
However the diagnostic file runs without any errors.
Only the last menue point of the screenshots "Change ColourID" isn't at my screen.
My ELFin is still bricked, maybe there is a special trick to unhide this menue entry
sandman01 said:
Only the last menue point of the screenshots "Change ColourID" isn't at my screen.
Click to expand...
Click to collapse
Same here.
sandman01 said:
Hi!
I test the file on my bricked Elfin.
Normal flashing via SD card is impossible because the bootloader doesn't start the flash process.
However the diagnostic file runs without any errors.
Only the last menue point of the screenshots "Change ColourID" isn't at my screen.
My ELFin is still bricked, maybe there is a special trick to unhide this menue entry
Click to expand...
Click to collapse
Try this version. Compatible with ELFIN & Add [Change Color ID].
911sniper said:
Try this version. Compatible with ELFIN & Add [Change Color ID].
Click to expand...
Click to collapse
Hey bro, what does changing Color ID do?
EDIT: Booting from elf0diag.nbh makes it go into a DIAG> prompt in MTTY. I don't know what commands to use though.
I think it's no use whit the MTTY. Many official tools are the elf0diag.nbh format.
911sniper said:
I think it's no use whit the MTTY. Many official tools are the elf0diag.nbh format.
Click to expand...
Click to collapse
When this one starts, it says "Please Input Password".
Note: You cannot start any ELF0DIAG.nbh from SD if you have a USPL installed; you have to flash a signed SPL first.
PLUS IT WILL HARD RESET YOUR DEVICE IMMEDIATELY AFTER IT STARTS UP, WITHOUT ASKING....
dsixda said:
When this one starts, it says "Please Input Password".
Note: You cannot start any ELF0DIAG.nbh from SD if you have a USPL installed; you have to flash a signed SPL first.
PLUS IT WILL HARD RESET YOUR DEVICE IMMEDIATELY AFTER IT STARTS UP, WITHOUT ASKING....
Click to expand...
Click to collapse
i never used these tools before...
can't help more...
Hi!
I testet the new diagnostic File, and now I can change the Color ID.
Black and Green are available.
Black change the MID to ELF030000
Green change the MID to ELF030001
The original MID can't be restored!?!?!?! (it was ELF030050)
Maybe there are more Versions of the diagnostic tool which change the device into other colors.
I make exactrly whatever is writen there but I get message:
Security level not cleared!
What I suppose to do to avoid this and to get into test?
Hi, dsixda!
Bro' I'm in trouble...
The device was in tricolor bootloader.
Untill i work with your onix 4.0 was OK! but I decide to go back. So I get in this state.
Around (few nautical miles) was not other with device like this... :-(
So please gi'me som instruction what I can to do?
I can download or recieve files. maybe is possible to recieve an image of Gold card unbricker? or something that allow to load from SD card or USB?
Write to me here or PM or on my e-mail.
malintzin said:
Hi, dsixda!
Bro' I'm in trouble...
The device was in tricolor bootloader.
Untill i work with your onix 4.0 was OK! but I decide to go back. So I get in this state.
Around (few nautical miles) was not other with device like this... :-(
So please gi'me som instruction what I can to do?
I can download or recieve files. maybe is possible to recieve an image of Gold card unbricker? or something that allow to load from SD card or USB?
Write to me here or PM or on my e-mail.
Click to expand...
Click to collapse
Why are you posting something off-topic here?
Post in the Onyx thread and mention your SPL/IPL.
sandman01 said:
Hi!
I testet the new diagnostic File, and now I can change the Color ID.
Black and Green are available.
Black change the MID to ELF030000
Green change the MID to ELF030001
The original MID can't be restored!?!?!?! (it was ELF030050)
Maybe there are more Versions of the diagnostic tool which change the device into other colors.
Click to expand...
Click to collapse
Really? I'm still at ELF010150 (I ran device_info.bat).. What does device_Info.bat say for you?
I dumped the USB port. (SnoopyPro + mtty)
There is also the change from ELF030050 to ELF030000
sandman01 said:
I dumped the USB port. (SnoopyPro + mtty)
There is also the change from ELF030050 to ELF030000
Click to expand...
Click to collapse
That's pretty cool.
Are there any shipped ROMs with this Model ID (so that you can use Gold Card)?
I flashed a new ROM on my fuze and after turning it on- it just gets stuck on the start screen! It says
Smart Mobility
Test Only
Not for Sale
And then i says the following on the right bottom corner:
R 1.02.25.32
G 52.39c.25.22
D 1.95.00.00
And the following on the left bottom corner:
U
I did a hard reset three times but it is still stuck~!! PLEASE HELP ME OUT!
prateeksach said:
I flashed a new ROM on my fuze and after turning it on- it just gets stuck on the start screen! It says
Smart Mobility
Test Only
Not for Sale
And then i says the following on the right bottom corner:
R 1.02.25.32
G 52.39c.25.22
D 1.95.00.00
And the following on the left bottom corner:
U
I did a hard reset three times but it is still stuck~!! PLEASE HELP ME OUT!
Click to expand...
Click to collapse
Reflash, basically same thing happened to me on my first flash...what rom did u use? etc etc, try another rom
meth0dGSX said:
Reflash, basically same thing happened to me on my first flash...what rom did u use? etc etc, try another rom
Click to expand...
Click to collapse
I want to do that! But since it wont turn on, I cant connect it through active sync or the WMDC, so i cant flash a new rom!!! Is there some other way????? PLEASE HELPPPPP
Did you follow the instructions and do the Hard SPL first? you can flash from the bootloader or a SD card, read up before u go flashing
meth0dGSX said:
Did you follow the instructions and do the Hard SPL first? you can flash from the bootloader or a SD card, read up before u go flashing
Click to expand...
Click to collapse
I did a hard SPL the first time i flashed a rom on my fuze! How do u flash from a bootloader or a SD card????? Can u tell or guide to where i might know?
prateeksach said:
I did a hard SPL the first time i flashed a rom on my fuze! How do u flash from a bootloader or a SD card????? Can u tell or guide to where i might know?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=448008
http://forum.xda-developers.com/showthread.php?t=410150
prateeksach said:
I did a hard SPL the first time i flashed a rom on my fuze! How do u flash from a bootloader or a SD card????? Can u tell or guide to where i might know?
Click to expand...
Click to collapse
Did you confirm it was un-locked? If you do not know what bootloader is you need to go the Wiki and definitely read up some more....you should not have flashed without reading that thoroughly....after enter bootloader and confirm if it is un-locked and then you can proceed...
Now i know all the stuff! I checked the bootloader and stuff i have a hard SPL and now im going to flash a new rom from sd card! hope it works!
prateeksach said:
Now i know all the stuff! I checked the bootloader and stuff i have a hard SPL and now im going to flash a new rom from sd card! hope it works!
Click to expand...
Click to collapse
You should be good to go then....
wow, I'm surprised so many people don't flash via SD.. only way to go in my opinion.. otherwise just asking for trouble eventually
Black6spdZ said:
wow, I'm surprised so many people don't flash via SD.. only way to go in my opinion.. otherwise just asking for trouble eventually
Click to expand...
Click to collapse
Why asking for trouble? I've been flashing via PC for so long, so many times (cooked firmware and radio), on so 4 devices.. I have not encountered a brick ever. in fact, most of the issues you can just go into bootloader mode and reflash again..
I did it and it worked! This is a way easier method! I like it!!! BUT I STILL HATE MY PHONE cause I had a G1 last week and it got stolen! I hate it when that happens. I only got to use it for one week! Some B***H stole it!
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.