Related
Hey peeps, hope somebody out there can help. I have quite a strange problem and have tried everything I know to sort it with no luck.
Ok before I start I just want to say I'm not playing the blame game, it was probably an unhappy coincidence it happened at the time it did.
I was on kingk's 2.0 hero rom, but decided i'd try maxisma's, so I wiped, formatted ext, flashed maxisma 2.0, then 2.0.1 which had just been released as a fix. Rebooted the phone. Everything was going smooth, I got a little flash of the notification bar same as what happens with every hero rom I've tried, then I got FC on messaging, then the phone froze. Thinking nothing of it, reboot, reflash after a wipe, but I repaired ext after wiping it. Flashed 2 and 2.0.1, then rebooted. Phone got to htc logo, then froze for a few seconds before going back to the animated android. Ok, this rom needs more time in the oven I thought.
I then wiped, formatted and repaired and flashed kingk's rom back to my phone, boot loop
I tried mlign, boot loop
I tried xrom, boot loop
I flashed htc image and then cyanogen's rom, finally got booted.
I've spoken with MikeTaylor (he has the patience of a saint, buy him a beer, I did) and he suggested clearing the dev folder, I tried and was prompted with "device or service in use" so that didn't work. I even thought going back to stock would help, but it didn't. I then thought it had something to do with the SPL, cyanogen's being the only rom not needing haykuros, so I flashed "the official donut" which also gave me a boot loop.
So here I am, asking for any suggestions, and I'm willing to try anything.
Many thanks in advance for any help, and I hope when I get fixed, this thread isn't used anymore, we don't want more people with my problem
The only suggestion I can make is recreating the partitions on your card using parted or something like that. I had the same problem as you going from Cyan to xROM, recreated the partitions and it was fine
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
senaia said:
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
Click to expand...
Click to collapse
Oh, I assumed that card wouldn't mount so it wouldn't matter if you couldn't back up
So what does fastboot erase do? Wipe out /system?
i was hoping somebody here could tell me that, i've never used fastboot other than changing the splash screen and that was done using a tool, so i didn't actualy use it lol. card mounts, the flash goes through ok, but it just never boots, unless it's cyanogen mod, which i've not used for about 2 months, xrom awesomeness got to me, but i decided to try out a few hero / sense roms while JAC was out of the office, and now i can't go back to it lol
Sorted, being lazy doesn't work. I used amonra recovery to make the partitions initially which worked, then had this problem. Tried using it again and it said it worked but I still couldn't flash. When I checked manually using parted, it showed 3 partitions. Fat32, blank, and swap. Recreated the partitions and I'm now back to full flashing fun. Unfortunate coincidence it happened right after flashing maxisma's 2.0.1
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S
Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
have a read here http://forum.xda-developers.com/showthread.php?p=30415128
Thx, but i just lost all hope, after i fixed everything.. Installed a stock 2.3.6 i tried to flash another cm10,by
Some doomsday dude and the camera wsnt working so i decided to try the other cm10 that bricked my
Device , after flashing it and gapps i pressed reboot system and after it went black to reboot i expected
The usual samsung logo but unfortunately it never came, the phone is now literally a brick, no sign of
Life i tried to get the battery off and press the power button for some minutes.. Nothin happens..
IceVip said:
Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
Click to expand...
Click to collapse
THIS - to go back to stock firmware
After flashing CWM and you get stuck in a bootloop into recovery, do THIS.
Additionally, read from HERE and HERE
Good Luck
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
eminence84 said:
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
Click to expand...
Click to collapse
JTAG has failed?
The emmc-chip has a special function for erasing partitions. this function is only useable by kernels over 3.x. it is bad that our emmc-chip has a bug. when using this function of the chip to erasing the data partition, the chip damages itself. the data partition cant be used anymore.
for more infos read in the threads and in the links for sgs2 and note.
if i'm wrong please correct me
So is there absolutely nothing I can do to recover my phone?
i would say no.
but if you store the data partition on ext.sd and make a rom that can use it, it is possible to use the phone as normal... like Ivendor did for a short time (if i'm right?)
Can you please detail the steps, what should I do?
Right now the phone is hard-bricked, absolutely no signs of life, can't enter download mode, nothing.
does odin detects your phone? nothing on the screen?
Not sure about Odin, but besides that nothing on the screen, not even when plugging the charger. I took it to a phone service to rewrite the memory with JTAG, and they said it hangs at about 20% and the memory is damaged. I don't understand, the phone is almost new, all I wanted was a lousy update from CM9 to CM10...
i assume that the problem at 20% was the damaged emmc data partition
edit:
but theres a big chance that i'm wrong and your chip is really fully broken. maybe you get the people at service center to be interested in your phone. maybe they can give you more information.
i don't know my phone is working.
what recovery had you installed to update? what did you do? wipe data/cache,... ?
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
edited my post...
eminence84 said:
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
Click to expand...
Click to collapse
yes, but you must be able to flash roms to your phone,.as example.by odin.
or the JTAG repair center can flash roms?
Probably they can, but I think I'll buy a JTAG interface and study this myself...
eminence84 said:
Probably they can, but I think I'll buy a JTAG interface and study this myself...
Click to expand...
Click to collapse
I think it takes a lot of time to know how things work...
what if your phone memory is completely dead? the you have bought the JZAG box for nothing...
but for sure it will be interesting how it works.
how much does such a interface cost about? (^^ more than a quarter of a phone? )
I found one at about 12$... I think it might be worth a shot
But yeah, I'm aware it would take some time until I can handle it well, and I'm not sure I have it.
I also considered buying another i9001, but I'm not sure what caused mine to fail, I want Android 4.1 in the new one, too, it really bugs me off I don't know the exact cause of the failure, so I won't repeat it again. I did everything exactly by the steps I found here on the forum, I used ivendor's ROM and updated CWM to 6.0.2.8.
be sure it is not only an adapter.
someone knows if you can write parts of the memory with something like these?
Hi guys I'm caught in a bad situation. I tried to install a ROM but it went bad so I booted into CWM and erased everything including /data and /system as well as /cache and everything else except for /0 amd /clockworkmod. I then proceeded to install another ROM but it went fine until halfway through it quit and went back into CWM. I didn't know what to do so I restarted the phone into the bootloader and just clicked factory reset hoping it would fix something. But it restarted and stayed on the HTC screen that has the development text and copyright warning on the bottom. It got stuck there for quite a while so I restarted the phone again and tried to go back to CWM but now it just flashes briefely before restarting itself to do the same thing over again! Help please I'm scared I might have bricked it
Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Edit: Using MiFlash and downloading the stock room from Xiaomi worked.
Minxxe said:
Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Click to expand...
Click to collapse
Try installing Stock Rom using MiFlash
gmoura5010 said:
Try installing Stock Rom using MiFlash
Click to expand...
Click to collapse
Yea, did that yesterday and that recovered my device. Still thanks for the advice.