Hello guys,
I have a very biug problem now.
I was with TeamICSSGS and I decided to move from it to Slim ICS.
But because I wanted to be fast I didin't read correctly and I didin't flashed the correct thing.
I flashed the I9000 Essentials and not the base which made the phone bootloop with the touch recovery.
Then I did a factory/data wipe and after the reboot there was no recovery and only bootloop.
Then I decided to flash a gingebread bootloader in the panic, don't know why I falshed it and it bringed me CWM Recovery of which I installed several ROM's with fail because they just stop installing when reac the kernel installation.
Then I downloaded http://forum.xda-developers.com/showthread.php?t=1685040 and flashed it, but with some recovery errors and bootloop again.
Can someone help me, please.
EDIT: I did that http://forum.xda-developers.com/forumdisplay.php?f=657 and it worked.
hey frnz i am new to this forum and i have only basic knowledge about the rooting process...
i have rooted my turbo last week now when i reboot it always stuck on the bootscreen... i have tried each and every method to sort this problem but nothing happens..
even i have factory reset my phone...
plz help me...
Try to flash the stock ROM
Rooting and Flashing methods can be found here.
http://forum.xda-developers.com/canvas-turbo/general/micromax-canvas-turbo-a250-t2508309
:angel:
sumitturbo said:
hey frnz i am new to this forum and i have only basic knowledge about the rooting process...
i have rooted my turbo last week now when i reboot it always stuck on the bootscreen... i have tried each and every method to sort this problem but nothing happens..
even i have factory reset my phone...
plz help me...
Click to expand...
Click to collapse
If you have CWM recovery try wipe cache/dalvik. If dont, flash stock rom with SPtools
I tried to install the AllianceROM_KK_v1, didn't know the ROM was a little more than 1.2GB, but my computer probably somehow shut the download to less than 700MB thinking it was downloaded completely. But when on safestrap, I didnt make any backup and just tried to flash it after factory resetting it. Obviously, it didn't sucessfully flashed it and now boot loop. Can installed the safestrap apk right from the recovery thing, I can't seem to get on the safestrap recovery. Can someone please help me soon as possible.
Khai.
khaino said:
I tried to install the AllianceROM_KK_v1, didn't know the ROM was a little more than 1.2GB, but my computer probably somehow shut the download to less than 700MB thinking it was downloaded completely. But when on safestrap, I didnt make any backup and just tried to flash it after factory resetting it. Obviously, it didn't sucessfully flashed it and now boot loop. Can installed the safestrap apk right from the recovery thing, I can't seem to get on the safestrap recovery. Can someone please help me soon as possible.
Khai.
Click to expand...
Click to collapse
You're going to have to do the MLG restore. See the link in my signature for info on how to do it and links to where you can get the stuff you'll need.
If you don't want to attempt the MLG restore, you'll have to go the the Samsung Experience Center at your local Best Buy and have them reflash it for you.
thankz man. I am working on it now. It's already 2:39 AM here now. real late. any way, thank you bro for the awesome prompt answer.
Hello All,
I've spent the last 6 months learning how to flash roms, realise you need the right kernel and made many mistakes which resulted in bricking my phone. I've learnt a lot and as you often suggest on this site, read and learn. I've been trying my best to do this over the months and have managed to even use Odin, after about 70 hours reading, track down a kernel XXLT to get my phone back into recovery and many other painful experiences.
I thought i had the basics down pat by now but i've bricked my phone this time and I'm truly stumped as it brings up an EMMC message and nothing i do with Odin or flashing kernels afterwards brings the phone back at all. I'm sure it's on here somewhere and you will point it out to me but I have tried as it's the only way to learn. Now, if you are willing, i could really benefit from some expert advice?
I have been running CM11 for the last week, really enjoying how it worked on my n7000. I was doing some further reading and came across the page for the Forest Kernel for CM11 on the n7000. I thought no problem, download file, follow flash instructions (wipe dalvik) and proceed as normal. But the zip file would not load and the recovery aborted. I was using CWM touch and in the malaise that followed, i now can't rememer which one it was but it was the grey screen one with the touch functionality.
I thought maybe i didn't have the right CWM to flash this file so I thought I would try a later version of CWM but use PHilz' touch version - using the 'about in recovery' it has v 6.0.3.7.
So i flashed the file again using Philz' version and then i just got a lot of fast scrolling text and I was stuck in recovery from that point on. I tried wiping for reinstall , installing raw kernels and everything i think i know about trying to fix it myself.
However, with lots of fast scrolling text going by, i started looking more closely at it and noticed this message:
Created filesytem with 11/32768 inodes and 4206/131072 blocks
warning wipe_block_device: wipe via secure discard suppressed due to bug in emmc.
now flash a new rom
Since this message, nothing works from the flashing a new ROM in recovery onwards. I just get message like cannot load .ini or failed to open zip etc.
Now i did spend time months ago reading about teh ICS emmc recovery problem but because I've been on 4.4.3 to begin with i thought I'd already surpassed the problem.
I've been running Slimsaber and recently CM11 on KK 4.4.4 so i didn't think i could initiate an 'emmc' problem.
So now i'm stuck and of course, bricked my phone just when i need it most. I only undertook flashing the Forest kernel because it seemed such a low level risk, wipe dalvik and flash.
If any of you could offer some advice, yes, even if you tell me to read it etc, I will understand. It's just after having taught myself so much from these pages I seem to have met my match this time in recovering my phone, so any advice or assistance will be appreciated.
I understand though if asking for this help is inappropriate.
Thanks in advance.
Regards,
Paul
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
ThaiDai said:
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Click to expand...
Click to collapse
Dear ThaiDai,
Sorry, when it goes wrong, it certainly is chaotic. The whole process of going wrong snowballs.
I'll try and follow your advice, thanks for your help.
Cheers,
nokiamodeln91 said:
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
Click to expand...
Click to collapse
Hello Nokiamodel. Thanks for your help. No, i didn't. As i ended up stuck in Philz touch recovery, I tried pushing a raw kernel on via Odin.
When i bought this phone, it came with Gingerbread on it so does that mean i should use gingerbread to return to stock?
cheers,
p
majaretilla said:
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
Click to expand...
Click to collapse
Majaretilla, thanks for this advice.
I was about to do this when i remembered reading somewhere on another forum that sometimes taking the battery out can sort something like this out. I took out the battery, and when i put it back in, it did not boot into philz touch recovery but what i now realise is the stock recovery. It's the one where you move the cursor by using power and volume keys.
This recovery flashed over the kernel and then roms I had onboard the phone until i got it back to CM11.
The only thing I can't crack now is why that Forest CM11 kernel won't flash using CWM or Philz. It gets aborted. I've tried v2, v4 and v5 and it never works.
I can't find out why or how to overcome the problem so I think i'll leave well alone. It's justfrustrating not knowing why it doesn't.
Thanks again for your help,
p
Boot loop on i9001, I tried everything but I guess not the right thing yet. I had CM11 installed but wanted to downgrade to Stock Rom gingerbread 2.3.6. I couldn't find any guides in that regard so I went on and with ODIN I flashed the phone to the stock rom, now it boots up forever, then I tried a boot loader fix, flashed that too, nothing. Re-flashed other stock roms, nothing.
It's stuck on a loop boot.
Can you please let me know what I could try? :crying:
Ok, try to re flash cm11 by following the same steps you did the first time you flashed it. Then find a guide to downgrade it to gingercake. Let me know.
Loop boot solved i9001
thanks you just gave me the idea of going to recovery mode and wipe all data and partition. After rebooting, 2.3.6 was there waiting for me.
Thanks me