Hey
Need some help here, i have put the vox USPL on my 710, flashed a rom which has a timebomb in it. So i have tried to flash 4 differnet roms to it but they all do the same thing. It goes to bootloader starts to flash hits 3% then reboots saying the rom is corrupt.
The ROM currently installed is Snap v1.2
Thanks for you help in advance.
Lordao
I just sorted it you have to flash your Phone with USPL 1.16.
1. Follow the instructions on : http://forum.xda-developers.com/showthread.php?t=409721 to flash your phone with USPL 1.35 CID Bypass
2. While the phone is in the mode started from the above instructions, download Vox-USPL-RUU.zip from http://forum.xda-developers.com/showthread.php?t=330909 and flash the USPL
3. Flash any rom as normal, thats how i got it to work.
Followed the instructions, gets to 100% then reboots and says it is corrupted. Now i cant use the phone becuase of the time bomb, i have to keep doing a factory reset which is a real pain cause if i sync i get the thanks for using this beta and the phhne is un uasable. Not sure why it wont update.
Lordao
I think the issue lies with SDA application unlock not working correctly
Related
Hi Guys,
Got my new V1615 from Vodaphone yesterday. I tried to flash the HTC shipped firmware, started SSPL-KAIS.exe once I realised it wouldn't flash without it. The flash failed at 17% and once it rebooted it going back into bootloader mode and wont let me flash any other firmware, stops at 1% and says "you cannot install this firmware on this device".
Download the original V1615 firmware that someone extracted but that just sits at 0% without flashing.
Any ideas where I can go next?
The-Kevster said:
Hi Guys,
Got my new V1615 from Vodaphone yesterday. I tried to flash the HTC shipped firmware, started SSPL-KAIS.exe once I realised it wouldn't flash without it. The flash failed at 17% and once it rebooted it going back into bootloader mode and wont let me flash any other firmware, stops at 1% and says "you cannot install this firmware on this device".
Download the original V1615 firmware that someone extracted but that just sits at 0% without flashing.
Any ideas where I can go next?
Click to expand...
Click to collapse
So you hardspl first then tried flashing or you forgot to read and do your research first.
No, I didn't HardSPL first. There are SO many people giving advice here it's hard to get the facts.
I've use mtty to get it to boot! WooHoo
So now I want to flash to the original 1.81 firmware. Do I need to HardSPL first or just load SSPL-KAIS and try again?
I'd really appreciate your advice on this!
OK, I ran Hard-SPL and it flashed correctly.
Thanks for the short but good advice!
Hello Guys.
About a lot of months i flashed TPCs Stocklike Rom to my device. Now i thought it might is time for an update.
But i got a huge problem :
When Flashing an other rom the device comes to bootloader and starts transfer/unpacking/whatever up to 100%.
After that my old TPC Rom reboots again.
What can i do?
Very much thanks for help
Copy the new rom that you want to flash onto the root of your sd-card and rename it to kaisimg.nbh. Reboot your phone into the bootloader and re-flash. That should do it.
Try flashing back to your stock rom first.
I already tried flashing the stock... that did not work for me.
Blinkydamo i flashed using the SD Card. The Screenshows update success.
Then i do a softreset an the old TPC rom boots again.
I already tried flashing the stock... that did not work for me.
Blinkydamo i flashed using the SD Card. The Screenshows update success.
Then i do a softreset an the old TPC rom boots again.
Any other ideas how to solve my problem ?
Put your phone into bootloader screen and see what it says for hardspl, maybe you just need to upgrade your hardspl.
3.29 - Flashing a new HardSPL doesnt work too
Most ROMS don't have new boot screens, some of the Chefs cook them in but others don't, are you sure it isn't just the old boot screen you're seeing, if the ROM flash has reached 100 % the Flash must have worked ?
StewD said:
Most ROMS don't have new boot screens, some of the Chefs cook them in but others don't, are you sure it isn't just the old boot screen you're seeing, if the ROM flash has reached 100 % the Flash must have worked ?
Click to expand...
Click to collapse
however,he says that he has flashed stock rom. stock rom changes splash with "smart mobility" black splash
Well is my phone unfixable ?
have you checked spl version in bootloader as denko7 said?
same problem
I am having the same problem.
MTTY says that BLOCK 1639 (0x667) is a bad block. Everytime I flash something (a new rom, stock rom, spl), it goes to 100% but it doesnt change anything as if i havent flashed. I am using TPC 11 rom, somtime it says that storage memory is full, and then when i do reset, everything is gone as if I did a master reset.
I am using TPC 11 rom
What SPL and Radio you have!?!?!
For me its spl 3.34 and radio 1.65.
i have HARD-SPL 3.29. Radio is 1.71.09.01
try to leave Sd card and flash with cable.
af974 said:
try to leave Sd card and flash with cable.
Click to expand...
Click to collapse
If you still have an old rom on your SD and put a new rom on there and try to flash, the phone will flash the first available file. If flashing using SD card , make sure that you have deleted all other rom image files first.
I was trying this how to :
http://forum.xda-developers.com/showthread.php?t=371154
but the commands listed are not working for my MDA Vario III (T-Mobile Brand).
For me task 8 = Reboot
I found out, that task 28 = Format
I got following output :
Code:
Cmd>task 28
Format start
Storage start sector=0x84C0, total sector=0x125C0
Storage start block=552, total block=1175
Total Bad Block in CE: 3
Erase physical block from 845 to 1999
si backup: Erase physical block from 2032 to 2048
But even after that im not able to flash a new rom.
Was that the right format?
I've installed for many different HD2, it's also OK. But when I intend to install Nandroid on HD2 Telstra It have a problem.
1. HSPL 2.08 is OK
2. Boot loader 1.13 MAGLDR113 is installed OK
3. Recovery is installed OK
4. Flash ROM Dorimanx ver 2.8.0.7. It run faster than ever and also inform that instalation is OK. But when reboot, It can't boot on to Android. It stop at 12345 Go Go Go!!! screen.
I've tried flash Radio with 2.15.50.xx but everything the same.
This problem only appear on HD2 of Telstra Operator, these other device are installed without any problem.
Anyone have some Ideas pls!
vtbinh said:
I've installed for many different HD2, it's also OK. But when I intend to install Nandroid on HD2 Telstra It have a problem.
1. HSPL 2.08 is OK
2. Boot loader 1.13 MAGLDR113 is installed OK
3. Recovery is installed OK
4. Flash ROM Dorimanx ver 2.8.0.7. It run faster than ever and also inform that instalation is OK. But when reboot, It can't boot on to Android. It stop at 12345 Go Go Go!!! screen.
I've tried flash Radio with 2.15.50.xx but everything the same.
This problem only appear on HD2 of Telstra Operator, these other device are installed without any problem.
Anyone have some Ideas pls!
Click to expand...
Click to collapse
Sounds like you've done everything right, try the link in my signature. Flash an official RUU and start from the beginning. That should iron out any issues leftover from your previous attempts. I assure you, the Telstra version is no harder to install to than any other.
Good luck!
Hi there,
i`ve got a problem with my HTC Sensation after trying to flash a new Radio to install ICS.
I have thought i´ve already been SuperCID, but this was false...
The recovery tried to flash the new radio, updated some parts of the software, but a failure occured and the updated failed because of the CID.
Since this update i cant boot into android.
There is the first Splashscreen, then a second the bootscreen, and then the splash screen...
I´ve already tried to restore my backup
Cleared Cache
Factory Reset
Dalvik cleared
etc
i´m very hopefull you guys could help me.
Luzifel said:
Hi there,
i`ve got a problem with my HTC Sensation after trying to flash a new Radio to install ICS.
I have thought i´ve already been SuperCID, but this was false...
The recovery tried to flash the new radio, updated some parts of the software, but a failure occured and the updated failed because of the CID.
Since this update i cant boot into android.
There is the first Splashscreen, then a second the bootscreen, and then the splash screen...
I´ve already tried to restore my backup
Cleared Cache
Factory Reset
Dalvik cleared
etc
i´m very hopefull you guys could help me.
Click to expand...
Click to collapse
Alright, firstly Hellow
Ofcourse when I read your problem, I deem that the "radio" you were mentioning is actually "Firmware"
If so, you seem to be having a similar issue which was solved in this thread. Nevertheless. Here's a way to fix it.
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/show....php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
THEN,
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ROM you wanted.
3. Boot & flash the suggested radio if you are using a ICS ROM.
Hope it helped!
Hi,
thank you.
Alright the steps for writing the CID are enough. Now it works again.
After writing my cid i could flash the radio and the ICS ROM.
It was a bit tricky to get adb to recognize my phone.
My phone seems to be turned of, but windows and adb said its on?
From this moment i was able to write the CID.
Thank you.
Luzifel said:
Hi,
thank you.
Alright the steps for writing the CID are enough. Now it works again.
After writing my cid i could flash the radio and the ICS ROM.
It was a bit tricky to get adb to recognize my phone.
My phone seems to be turned of, but windows and adb said its on?
From this moment i was able to write the CID.
Thank you.
Click to expand...
Click to collapse
So I take it that the problem is solved and you are able to run your device normally?
I realised that I forget to include the link for the guide LOL.
Yes right, i have just flashed a new ROM, its booted and runs well.
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel