Whenever I try to run the RUU, I get this:
----------
usb
v2.01
upgrade
radio stack
please wait
-----------
Nothing will go, No % from PC and from Device. After some minutes, I get the 114 Error.
I tried to downgrade the boot and Now I ve v1.01 but still I cant manage to get it Upgraded.I tried two Roms with no Lucky.
Any Idea???
Ok, try going into bootloader mode and then try the upgrade. the task 28 55aa formats the ROM(including extended ROM). It however, does not formats the radio ROM
There was no need to downgrade the bootloader unless you're using <v1
What I ll suggest you is flash some OS.nbf first. Then, grapple with the radio stack thingy
kdskamal said:
Ok, try going into bootloader mode and then try the upgrade. the task 28 55aa formats the ROM(including extended ROM). It however, does not formats the radio ROM
There was no need to downgrade the bootloader unless you're using <v1
What I ll suggest you is flash some OS.nbf first. Then, grapple with the radio stack thingy
Click to expand...
Click to collapse
Thanks for the advice.
Boot was 2 before.
I tried to put in the folder one by one the 3 files but still my upgrade bar or flashing % cant run. The device screen will change showing as if the flash is running but no % and ten min or so i will get Error 114.
I tried all reset but still cant get it run. But the Bootloader updater exe can be load in the device .
??? Any other Idea???
I m still facing the same problem.
Can someone explain me this log:
----------------------------------
03:35:02:343 [msg] : Version : [2.11].
03:35:02:343 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
03:35:06:421 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
03:35:10:484 [msg] : Disconnect ActiveSync .... [2]
03:35:10:484 [msg] : Start Get Connect Port.
03:35:10:656 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
03:35:32:140 [msg] : Get Device Backup ID.
03:35:32:140 [msg] : Device BL VER : [1.01 ] [].
03:35:32:140 [msg] : Device ID Is Incompatible.
03:35:32:140 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
03:35:34:421 [msg] : Check Ac in BL mode. AC : [1]
03:35:35:921 [msg] : IsBL. BL : [1]
03:35:36:000 [msg] : =============================================
03:35:36:000 [msg] : START UpdateRadio !
03:35:45:000 [msg] : Check Radio Level 0 [704].
03:35:46:578 [msg] : RUpgrade 0 : 0 Start.
03:40:37:312 [err] : RWipe Data Error.
03:40:37:781 [err] : BL UpdateRadio Error.
03:40:37:781 [msg] : START UnInitialization !
03:40:37:796 [msg] : END UnInitialization !
03:40:37:828 [msg] : IsBL. BL : [1]
--------------------------------------------
I m looking also for bootloader 2.01 for the Universal or boot 1.04
Thanks.
blaiseid said:
I m still facing the same problem.
Can someone explain me this log:
----------------------------------
03:35:02:343 [msg] : Version : [2.11].
03:35:02:343 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
03:35:06:421 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
03:35:10:484 [msg] : Disconnect ActiveSync .... [2]
03:35:10:484 [msg] : Start Get Connect Port.
03:35:10:656 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
03:35:32:140 [msg] : Get Device Backup ID.
03:35:32:140 [msg] : Device BL VER : [1.01 ] [].
03:35:32:140 [msg] : Device ID Is Incompatible.
03:35:32:140 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
03:35:34:421 [msg] : Check Ac in BL mode. AC : [1]
03:35:35:921 [msg] : IsBL. BL : [1]
03:35:36:000 [msg] : =============================================
03:35:36:000 [msg] : START UpdateRadio !
03:35:45:000 [msg] : Check Radio Level 0 [704].
03:35:46:578 [msg] : RUpgrade 0 : 0 Start.
03:40:37:312 [err] : RWipe Data Error.
03:40:37:781 [err] : BL UpdateRadio Error.
03:40:37:781 [msg] : START UnInitialization !
03:40:37:796 [msg] : END UnInitialization !
03:40:37:828 [msg] : IsBL. BL : [1]
--------------------------------------------
I m looking also for bootloader 2.01 for the Universal or boot 1.04
Thanks.
Click to expand...
Click to collapse
What Rom are you flashing and what device do you have?
It would appear you are flashing the wrong Rom for your device.
If you are sure the Rom is for your device then try either flash from BootLaoder with NO-ID flash tool or SuperCid your device.
Cheers,
Beast
beast0898 said:
What Rom are you flashing and what device do you have?
It would appear you are flashing the wrong Rom for your device.
If you are sure the Rom is for your device then try either flash from BootLaoder with NO-ID flash tool or SuperCid your device.
Cheers,
Beast
Click to expand...
Click to collapse
Thanks for your Support mate.
-The Device is an I-Mate Jasjar.
-It was on NO GSM
-Was switching On fine showing Orange Brand.(Was Longtime Flashed to M5000)
-After Mtty (task 28 55aa) No more Booting but could show Bootloader serial -v2.01 if i put it in that mode. It could enter Hard Reset (press 0 for factory restore or X to exit if i try hard rest "after mtty").
-When trying to upload the Jasjar RUU nothing happens.
** Now the device cant enter bootload mode any more.**
I m confused.
Related
SORRY GUYS...ITS WORKING PROPERLY..WAS OVER LOOKING A SIMPLE STEP..
THANK U GUYS..
Hey guys,
I was trying to install custom ROM on my Diamond and now, all i am seeing the standard Touch Diamond black screen and nothing beyond that.
Here are the steps which i followed:
1. Downloaded HARD SPL from http://forum.xda-developers.com/showthread.php?t=416211 and ran ROMUpdateUtility.exe on the phone. It was successfull
2. Then downloaded custom Radio 1.09.25.23 and installed on the phone jst as the previous step. Even that was successful.
3. Downloaded MTTY from http://forum.xda-developers.com/showthread.php?t=540290 and tried flashing from USB (post #4).
3.1 in the bootloader, selected USB and left every other configuration like original.
3.2 in the cmd :
--------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
--------------------------
then,
--------------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 75 FAIL !!!
ERASE block 123 FAIL !!!
ERASE block 138 FAIL !!!
ERASE block 1075 FAIL !!!
ERASE block 1667 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
------------------------------
then,
---------------------
Cmd>task 8
Cmd>
---------------------
disconencted my device and held the vol down key and was navigated to the bootloader screen with USB connection.
4. dowloaded 'Energy' ROM from http://forum.xda-developers.com/showthread.php?t=517300
and then tried running it.. but then the custom RUU says that cant connect.
Now i am really worried..did i brick my cell? is there any way to come out of this??
Loads of thanks in advance..
I had installed the latest version of CM 10.2 and when i tried to go back to stock, the KDZ updater does not work.
I get the message that battery power is less (my battery is charged 70%).
How can i go back to stock. Please help
This is message in flash tools
03:45:15 : Phone type Compare start
03:45:15 : *****Start _GetBatteryLevel*****
03:45:15 : ******************************
03:45:15 : Battery(2)
03:45:15 : You can't continue the process due to lack of battery power.\nRecharge the phone battery fully and retry.
03:45:24 : ~~~~~~~~~~~~~~~~~~~~
03:45:24 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
03:45:24 : Page_Error ºÎºÐÀÔ´Ï´Ù
03:45:24 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
help
veenab said:
help
Click to expand...
Click to collapse
i solved the issue. What i did was format the system, data, etc from recovery , then download mode, flashed the original stock .
hi pls share htc e9+ flashtools firmware
phone is soft breack
Operation : Check / Read Info [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6795
BB_CPU_NME : [MediaTek] Helio[X10]|MT6795_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
[DA_ERROR] : SECURITYBOOT_BOOT_NOT_ACCEPTED
Boot Error!
Operation Failed
Elapsed: 00:00:28
Reconnect Power/Cable!
Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted
sumit_trivedhi
sumit_trivedi said:
Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
I had same problem.
Root and repair imei any Qualcomm tool ..
Recently, I discovered that I had this old device in my drawers so I decided to take it out to see if I could get it running. It wasn't charging or turning on at all, so I took the back off and replaced battery and connector, nothing. So, after plugging it in to my computer, I noticed a weird device named "CLOVERVIEW", which searching that up, is usually associated with ASUS devices, which is really weird. I followed a guide to repair a dead boot, using a zip file provided here.
I put the files into the correct spots in Phone Flash Tool 4.4.4, yet I only receive an error when flashing. It appears the IFW file flashes fine, but the DnX FW does not. Log provided below.
----
06/20/23 23:13:48.280 INFO : Loading Flash file ...
06/20/23 23:13:48.280 INFO : Ready to flash!
06/20/23 23:13:49.317 INFO : Port 0/4: Start flashing BLANKPHONE flash file for
06/20/23 23:13:49.317 INFO : Port 0/4: IFW flash started - SN : CDC36BFD990D9446
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 0
06/20/23 23:13:49.361 INFO : XFSTK-STATUS Detecting Intel Device - Attempt #0
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 5
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FW download is in progress ...
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-PROGRESS SN: CDC36BFD990D9446 3
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Softfuses Binary absent. Please provide binary.
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FAIL
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Errors encounter during FW download. Aborting ...
06/20/23 23:13:50.491 INFO : Port 0/4: IFW flash success - SN : CDC36BFD990D9446
06/20/23 23:16:51.438 ERROR : Port 0/4: Device on port 0/4 timeout to enum adb (TIMEOUT = 180)
----
I'm not exactly sure what to do from here, the device still appears in Device Manager and I can't do anything about it from this point.