Long story short. Im using Infinix Hot 11s X6812 V728, wanting to root it with little to none knowledge. Flashed wrong boot.img, gets me to bootloop. Tries to flash stock rom but V728 firmware is not yet available. Flash stock rom of later version, now doesn't bootloop but after logo ot goes straight fastboot.
Installed TWRP and found in reboot/system options No OS Installed.
Tries to flash the later version again which is V723. Twrp is gone, stock recovery is in, only to found out the build version of my device is V586-V573 something like that. Tried to manually flash boot.omg, nothing happen. Thought to take it to carlcare but orange state. So tried to lock oem. Now logo bootloop with red state line. Does carlcare will know if you play with bootloader? Do i have another options?
IllustriousKage said:
Long story short. Im using Infinix Hot 11s X6812 V728, wanting to root it with little to none knowledge. Flashed wrong boot.img, gets me to bootloop. Tries to flash stock rom but V728 firmware is not yet available. Flash stock rom of later version, now doesn't bootloop but after logo ot goes straight fastboot.
Installed TWRP and found in reboot/system options No OS Installed.
Tries to flash the later version again which is V723. Twrp is gone, stock recovery is in, only to found out the build version of my device is V586-V573 something like that. Tried to manually flash boot.omg, nothing happen. Thought to take it to carlcare but orange state. So tried to lock oem. Now logo bootloop with red state line. Does carlcare will know if you play with bootloader? Do i have another options?
Click to expand...
Click to collapse
Some rules of thumb:
0. If you don't have a solid grasp on what you're doing, and how to fix it if something goes wrong, don't try.
1. Don't try to mess with anything without an unlocked bootloader.
2. NEVER attempt to lock the bootloader unless your device is running bone stock firmware, and successfully boots.
3. Don't expect warranty repair of any kind if you screw up the firmware. This may not be the answer you want, but what you did to your device is your fault.
They will probably fix it for you, but you will likely have to pay for the repair.
Related
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
Correction2:
Flashed back to stom rom, and will install root again today, this was really frustrating. I guess it just isn't going to happen.
Correction, after many tries, it did react to the button combo. I formatted everything from CWM and reflashed the first rom. Now there's only a wifi problem. It simply does NOT turn on wifi, ever. From the notification bar it turns off right away, from the settings-wifi screen it turns on and keeps saying turning on wifi.
What now? Since this rom now works, I don't really want to go to another rom to fix wifi.
Also we just noticed the sim is not detected! It doesn't ask for pincode, can't call or anything.
I have a GSM One X+ and I wanted to flash a new rom.
What I did was unlock the bootloader via HTC dev, flashed CWM, flashed the SU zip, and it booted into the stock rom fine. However, wifi stopped working.
To fix the wifi problem, I first tried this rom:
http://forum.xda-developers.com/showthread.php?t=2044584
That booted, but still wifi problem.
Then flashed this:
http://forum.xda-developers.com/showthread.php?t=2068901
From CWM, I could not find the way to go to bootloader (to flash boot.img) so I used voldown+lock to restart and go into bootloader to flash the boot.img
That didn't work, got a error every single time (cannot load boot.img unknown error)
I'm 100% sure I did it the correct way, however at that point I could not enable USB debugging yet because android hasn't started in the new rom at that point.
So I went to bootloader and tried flashing the boot.img many times, but it just kept giving errors. The rom wouldn't boot either.
Then I tried re-flashing the first rom, because that booted at first.
That first rom is now stock at the bootscreen, and it doesn't do anything, it doesn't react to voldown+lock either.
What to do now? Can't pull battery and button combos don't work either.
When you are in bootloader, can you write what is written right under *** UNLOCKED *** ?
Lucky Thirteen said:
When you are in bootloader, can you write what is written right under *** UNLOCKED *** ?
Click to expand...
Click to collapse
It is a phone of a friend, he was here 4 hours while I tried everything.I rooted at least 5 phones and installed roms on them so I expected it to work. However there were so many problems we gave up.
We reinstalled the stock rom, and re-rooted.
First rom didn't have any wifi,
Second rom didn't boot because I couldn't flash the boot.img even manually.
At random times, the phone didn't react to ANY input, not even hard restart.
So we gave up. He is now back to stock+root. Might try again some time, when there are better stable roms with included boot.img files.
Delano.888 said:
Might try again some time, when there are better stable roms with included boot.img files.
Click to expand...
Click to collapse
There is plenty of stable ROMs available. Probably you didn't pick the right phone version. Can you confirm how the phone is identified by EVITARE_UL or ENRC2B?
Lucky Thirteen said:
There is plenty of stable ROMs available. Probably you didn't pick the right phone version. Can you confirm how the phone is identified by EVITARE_UL or ENRC2B?
Click to expand...
Click to collapse
Actually I cannot, the friend & phone is not here anymore. Thus this thread is now pointless, sorry.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).
Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
TForsman said:
Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
Click to expand...
Click to collapse
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Jhon998 said:
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Click to expand...
Click to collapse
Thanks, worked fine to use flashtool to get it to work again. Installed recovery and rooted it. Also custom rom. Thanks again