Help, phone randomly enters bootloader upon restart? - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

Ok im having a problem where my phone will randomly enter bootloader upon restarting it and will not load rom. its acting like there is no rom there, yet if i take out the battery and plug the phone into power then restart it will load the rom... very weird. I have had the same rom on this phone for about a week now and this is the first time its done it with this rom, though it did do it with a previous rom(both dutty roms). I am going to load the Stock Rom on it and see what that does.
Any help would be greatly appreciated.

Most likely are RUU flag. You can use MTTY & issue commands to be sure:
1. cmd>info 8
(save the MTTY screen return & post it or PM me)
2. cmd>set 16 0
(will give you "cmd>" again)
3. cmd>boot

same problem
hello,
I had the same problem with my original rom, i now installed the L26_WM_6.1_PRO_V3_CUBE_(3.51.502.0_WWE) rom, and all problems are gone:
those problems were:
* short battery time
* poor bluetooth connection with my car
* bootloader screen on reset
* slow active sync
i am gonna try the vanilla release this week
grtz

Here is what MTTY gave me if anyone can make anything from it.
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8A00
Partition[3], type=0x4, start=0x9780, total=0x11B40
CE Total Length(with sector info) = 0x4C0BC00
CE CheckSum Length(without sector info) = 0x4BC0000
***************************************************
also when in bootloader my tilt says
KAIS1*0 MFG
SLP-1.0.0liPof
CPLD-8
dont know if that helps

Looks like everything is okay. Maybe a bad flash. Try flash via SD card.

ive updated twice from dutty 29 april to tnt, both no go. But both were from pc...updating tnt from sd card will update soon

still no go....i have no idea what it could be.

I had the same problem with my hermes. It happened when the battery was low so i made sure my device was always juiced up. then it would happen randomly (but only when battery was under 30%)
I got a new cheap battery off ebay to test it out and that battery is now holding up better then the OEM one.
So try your luck with a new battery..
Hope this helps.

Related

My ATT Tilt stuck in Tri-Color

here is the info on the screen itself
KAIS1*0
SPL-1.56.0000
CPLD-8
on the top right corner "RUUNBH"
I tried unlocking it using POF's simunlocker then i get stocked here
MTTY doesnt even see USB
MY PC sees it though but not activesync
what i've done to resolved
1. search for answer google and here.. no dice
2. leave the battery for .03 and 1 day respectively.. no dice
3. reset it.. no dice
need help badly...
do a search for stuck in boot loader
Take a look at this pof post... perhaps helps you...
http://forum.xda-developers.com/show...03&postcount=1
digi0123 said:
do a search for stuck in boot loader
Click to expand...
Click to collapse
it is on my #1 as you can see.. thanks..
fitdocsr said:
Take a look at this pof post... perhaps helps you...
http://forum.xda-developers.com/show...03&postcount=1
Click to expand...
Click to collapse
hey genius thanks!! got it to work!!!
iseedeadpeople said:
it is on my #1 as you can see.. thanks..
Click to expand...
Click to collapse
if mtty doesn't see ur phone than i suggest u send a nice and polite pm to gsleon3 and solicite his help.
thesire said:
if mtty doesn't see ur phone than i suggest u send a nice and polite pm to gsleon3 and solicite his help.
Click to expand...
Click to collapse
thanks!! I did unlocked my old phone before 8525 in here but now it seems that the kaiser is much more difficult..
where is the step-by-step wiki to unlock my phone?thanks...
ok now i got my device to reboot...
but now if i turn-off or reset my device, I have to use mtty and use the boot command to turn it up again because it goes back to tri-color screen.. Thanks...
also it wouldnt sync anymore...
update:
now it wouldnt even do a reboot in mtty it just shows white screen and then randomly display the tri-color every 2 mins.
iseedeadpeople said:
update:
now it wouldnt even do a reboot in mtty it just shows white screen and then randomly display the tri-color every 2 mins.
Click to expand...
Click to collapse
Buddy, I'm saying this because In all honesty I'm a nice person. You are going to get on people nerves if you don't start Searching More and Longer and/or posting you question in the already relevant thread.
For example, if you are trying to Unlock Post in the Kaiser Unlocker Thread. If you are stuck in boot loader, post in the Stuck in bootloader thread. It's just a common courtesy thing we have going on around here.
+1 to what jimmy said and i strongly advise you to stop playing with mtty and contact gsleon3
first off, the big no no which you tried to do some type of flashing without HardSPL. You first gotta jumpspl and then hardspl. If that doesn't work, then welcome to the newbs bootloader club and i sense a pm to gsleon3 will be coming very soon.
LOL, The more stubborn they are, the harder the fix can be. Stop screwing around & contact GSLEON3, LOL.
ok i will post there now...
just quick it is up again back to the normal screen, now how do i resolved this?Thanks.. what diagnostic tests or repairs i should do??
GSLEON3 said:
LOL, The more stubborn they are, the harder the fix can be. Stop screwing around & contact GSLEON3, LOL.
Click to expand...
Click to collapse
you got pm
here is my info 8 result
info 8
--- 2K bytes sector version ---
DEVICE NAME=hynix_hyh0ssj0mf3p
DEVICE ID=0xBA
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x9E40
Partition[3], type=0x4, start=0xAB80, total=0x10740
CE Total Length(with sector info) = 0x5615C00
CE CheckSum Length(without sector info) = 0x55C0000
thanks..
I just had a very weird thing. Not sure if this has happened before. My phone has never had any problems. I use SPB mobile shell and was just installing a new theme. Like usual I restarted the phone after copying the files and the tri-color screen came up. I soft-reset the phone a number of times and the tri-color screen still came up every time. Took out the battery let it sit for a minute and started up, again the tri-color screen appeared. Finally I figured I would plug it in to my wall charger. It changed from serial to USB, so I soft reset it and it booted up fine.
This is very odd. Just wanted to give my input. I'm sure this has happened before but I don't remember reading about it.
*EDIT: OK I'm still having the problem. WHen I try to restart my phone, it goes to the tri-color screen. I have SPL 3.29 installed. When I'm on the tri-color screen, it says I have 3.29. Why is it doing this to me. To get it to boot, I have to remove battery, put battery back in, plug it into wall charger, and then turn on phone. THis is the only way I have found to fix it. Anyone???

Cruise to Brick transformation? HELP?

In the process of updating my brand spanking new Cruise, the flashing stopped at 14%. I waited one hour, and still at 14%, so I reset the device. Now, I get the multicolored bootloader screen.
I tried the following:
1) Updating with the orginal roms, but get an 294 INVALID VENDOR ID error.
2) Copying the .nhb file to a micro SD, then resetting, but get and 000280002 Not Allowed error.
3) Copying hardspl to the micro SD, then resetting, but it stays in the "Loading" screen and never changes.
4) Using mtty and entering the password command. It just returns a bunch of garbage (like HTCI(0 332). Its different every time I try it.
5) Prayer.
6) Holly water.
7) Vodo.
I cannot bring it back to life. Can any of you HTC gods help me?
try to copy the .nbh file from hard spl to the root of your micro sd card and rename it to POLAIMG.NBH and then hold the camera button firmly, hit the softreset button and when you see the tricolor screen, release the camera button. hopefully it will ask you to hit the power button to start installing the hard spl.
if that works fine, take the .nbh file of a cooked rom here (i would suggest udK Vega or Diamond) and do the same with that.
i hope it works for you, it would be my way to try if my device is bricked like that.
As soon as I press and release reset the screen goes to the tri-color, then turns gray with the word "Loading...." on it. The happens the same no matter the state of the camera button (down or not). It sits at the "Loading" screen.
I waited a minute or two for something to happen, but it never does.
ok, too bad that didnt help :|
Using mtty, and typing the command "info 8" returns the following:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 1093 (0x445) is bad block
Partition[0], type=0x20, start=0x2, total=0x3E
Partition[1], type=0x23, start=0x40, total=0x780
Partition[2], type=0x25, start=0x7C0, total=0x9480
Partition[3], type=0x4, start=0x9C40, total=0x11680
CE Total Length(with sector info) = 0x4E6E200
CE CheckSum Length(without sector info) = 0x4E20000
So, it looks like block 1093 is bad. How do I fix it?
Oh ****, I think I found a solution
using mtty, I did the following:
1) type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
2) type "task 8" , at which point my cruise booted!
THEN I QUICKLY FLASHED HARD SPL!!!!!!!!!!!!!!!!!!!!
Hope this will prevent any further stupidity on my part!!

XDA Orbit 2 loads to bootloader. Can't update

Hello all,
Some time after adding my Orbit 2 to my home WiFi last night (it was in my pocket so I didn't see exactly when) it rebooted itself and stayed at a red, green and blue screen (which I now know is the bootloader screen).
I tried a soft and hard reset but it made no difference.
I downloaded RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship and tried to flash the ROM. Before the install, at the part where you click the "Update" button, the "Image Version" label for my device is blank i.e. "Image Version: ". Although it installs to 100% and tells me it's successful it still stays at the bootloader screen.
I tried downloading Hard SPL v2 but it gives me an Update Error code 262. I go through the recovery steps and try again but the same thing happens. Although in the recovery stage when asked to reattach the device it is only recognised if I hard reset. If I power on normally Windows gives the "This device is not recognised..." balloon.
I've searched the forums here for an answer but couldn't find a similar problem (Apologies if I'm wrong and there's a similar thread)
Here's the mtty info 8 information:
--- 2K bytes sector version ---
DEVICE NAME=hynix_hyh0ssj0mf3p
DEVICE ID=0xBA
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 647 (0x287) is bad block
BLOCK 1652 (0x674) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x780
Partition[2], type=0x25, start=0xDC0, total=0xBA00
Partition[3], type=0x4, start=0xC7C0, total=0xEB00
CE Total Length(with sector info) = 0x6443E00
CE CheckSum Length(without sector info) = 0x63E0000
I've been trying to solve this for the past few hours but now i'm out of ideas.
Thanks for reading and any help is highly appreciated.
Danny
Problem Resolved
Hello All,
The solution (At least I think) was to flash the ROM to the latest version and then remove the battery for at least 36 hours. Maybe just leaving it without power would have produced the same results.
When I powered back up the splash screen showed but hung there. I performed a hard reset and the dialog box with the "Hard resetting will remove all information from the device". I clicked yes and it wiped my device. Took about 10 minutes to reboot after that but been fine ever since.
So apart from loss of information all is well again =)
Just thought I'd post incase someone else comes across the same problem in the future.
Cheers,
Danny

I'm stuck at the boot loader =(

I just bought an ATT Fuze and the other day when driving home from work, I went to look at it and it was off. It won't turn back on except to the boot loader screen.
I haven't custom flashed anything onto this phone. It's running the standard ROM so my PC won't recognize it as a phone, but as a device.
I've tried to follow the advice about another phone stuck at the boot loader, but to no avail. Please help as this is a very nice phone and I'd like to get it up and running again. Thanks in advance.
Note: Hard reset doesn't work. Unaware on which buttons will do a soft reset, but I doubt that will work.
Note 2:
Cmd>info 2
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 LC card
SD Clk rate 24 MHz
SD Init OK
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 LC card
SD Clk rate 24 MHz
SD Init OK
HTCSSuperCIDHTCE
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 32 (0x20) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x900
Partition[2], type=0x25, start=0xF40, total=0x13E80
Partition[3], type=0x4, start=0x14DC0, total=0x26200
CE Total Length(with sector info) = 0xA786E00
CE CheckSum Length(without sector info) = 0xA6E0000
To soft reset, all you need to do is push the stylus in the little hole on the bottom of the phone just to the right of the usb port (not the one above the port-that's the mic). It's confusing, cuz it has a little headphone icon above the hole, but that's it. Weird that the phone went into bootloader, but that's the normal way to get out of it (doing a soft reset). You can also try pulling the battery for a few minutes.
Sounds like the best thing to do in your case is just to download the stock ROM (http://www.htc.com/us/SupportDownload.aspx?p_id=198&cat=2&dl_id=553 for an AT&T fuze) and reflash (just run the app with the phone connected, it'll tell you what to do).
Hopefully, your main ROM is just corrupted and that'll fix it.
Its telling me to establish a connection with active sync, but I can't since the phone wont go past the boot loader. Is this okay?
Another note: The phone doesn't boot straight to the boot loader, it wont boot at all unless I hold power and volume down, then it goes to te boot loader.
The upgrade should run fine without an active-sync connection if the phone is connected properly in bootloader mode. The RUU (Rom Upgrade Utility) is designed for recovery purposes (i.e. device disconnects mid-flash.)
Just keep clicking 'next', then 'upgrade'. Don't worry if it doesn't show a version of the OS installed, it just can't tell without an ActiveSync connection. This is normal.
(Additionally, you can try extracting the NBH file from the EXE upgrade archive and flashing via MicroSD. Search the forums for more info.)
Still no luck. Updates went through and both ways it said that they were successful, but the phone still won't boot.
Mine had the same problem, just call AT&T and tell them. I had my replacement the very next day since I called before noon.
Right, but since I bought mine used, I don't believe I'm covered by warranty.. Should I send it in to get repaired by a third party company, or will this thing still be under warranty from ATT or HTC?
enkazy said:
Right, but since I bought mine used, I don't believe I'm covered by warranty.. Should I send it in to get repaired by a third party company, or will this thing still be under warranty from ATT or HTC?
Click to expand...
Click to collapse
If it's less than a year old, don't tell them you bought it used and you should be fine. If not, add insurance on your AT&T plan [I think it's $4.99?] and the replacement is either free or $50, I don't remember which. better than shelling out hundreds for a new phone I guess!

solving hardspl hanging at 0% while flashing + video

I am really having a hard time flashing trying to flash hardspl on my Kaiser.
I have searched, followed guides (http://forum.xda-developers.com/showthread.php?t=433835) , watched videos (http://tiltmobility.com/how-to-flash-a-rom-video-new-version/) but I keep having troubles. I hope people can help me solve it and then this topic can be linked to from tutorials as a troubleshooting solution.
The problem: when flashing hardspl the actual flashing hangs at 0% in the white screen.
Here is what I have done:
- I have removed sim, sd card and battery (for 10 minutes)
- tried the all in one unlock app by olipro (the softspl version does not work)
- tried multiple softspl versions only 1.56 seems to get to the flashing (white screen)
- tried multiple hardspl installer versions
- have done a hard reset
- tried with and without phone password
- Tried another pc
About the phone:
- It is a kais130
- dutch orange branded wm6.0 (other/newer roms not available, reason for unlocking)
- sim unlocked with the original unlock code from the operator
About the pc:
- windows xp dutch
- sp3 with all updates
- activesync 4.5.0 build 5096
- syncing is not a problem
other posts by other people who had this problem either gave up or never posted a solution.
Here is a youtube movie with a demo of the problem, skip to about 3.30 to see the error, the rest is just showing what i did to get to the 0% error: http://www.youtube.com/watch?v=Nbik4E7vqqU
edit: at 4:45 it also shows the error the flash app shows on my pc screen.
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
I noticed that you either didnt do number 2 and did 9 & 10 backwards. redoing it this way.
zelendel said:
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
I noticed that you either didnt do number 2 and did 9 & 10 backwards. redoing it this way.
Click to expand...
Click to collapse
thank you for looking into this case.
as of #2 you can see the sim and sd card laying on the left they are already removed before turning the phone on. inserting the removed battery is the begin if the video (though looks awkward with one hand)
9 and 10 could be backwards on this try, some tutorials reverse this i think. i think the critical part here is it being disabled before you start the flashing. i will try once more and report back but i think that is not the problem.
EDIT:
tried it again this time doing 9 and 10 in the correct order but also on a different machine. just in case windows vista works better (always nice to use other peoples laptops for experimenting)
machine info:
- windows vista SP2 dutch with all updates
- mobile device centre 6.1
- starting hardspl with right-click > run as administrator
anything else i can try?
ok continuing to get more info from my device.
i am now using jumpspl + MTTY. using "info 8" i got this info
Code:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 623 (0x26F) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8B40
Partition[3], type=0x4, start=0x9880, total=0x11A40
CE Total Length(with sector info) = 0x4C8C400
CE CheckSum Length(without sector info) = 0x4C40000
Cmd>
now this "BLOCK 623 (0x26F) is bad block" seems .... bad ... is it? now what to do?
edit: everyone seems to have bad blocks, it is normal :S
other results from mtty:
- getdevinfo:
Code:
GetDevInfo: Get CID OK
HTCSKAIS1300OAG0HTCE
info2:
Code:
Card inserted
don't know what card is inserted but it ain't a sim or sd card, after this command mtty and/or my phone crashes
after more fiddling around in my phone i notice the amount of call time (incoming/outgoing calls) is still at the level it was before the hard reset. is this normal or did my hard reset go wrong?
fixed (sort of)
just a little message for future people with this problem (and used the search).
a friend of mine was planning on selling his tytnII and i was still having this ****ty problem, so we swapped phones.
the other one (dutch vodafone) had no troubles installing hardslp, it was a breeze.
unlocking was easy and i am now looking for rom's. so i hope nobody else aver has this problem, pm'ing me for a solution will not get you results
Same Problem
Today im trying to do the same thing with my kaiser... and i have the same problem... i did a lot of research, i guess im gonna give up
eltoze said:
Today im trying to do the same thing with my kaiser... and i have the same problem... i did a lot of research, i guess im gonna give up
Click to expand...
Click to collapse
Device's reserved kernel storage has bad block and thats why it causes your phone to stall at 0%.
Try installing android kernel, if you already have Hardspl v3.29 or higher. If it gets installed you can run OS from SD card
can someone help me? I flash my tytn without using the hard spl, and now caught in the smart mobility screen. what do I do?
Thanks ......

Categories

Resources