Related
So I have a problem with my Kindle Fire, I have it rooted and have clockwork recovery installed, I was able to flash MIUI rom a few months back with no problem, then switch back to Amazon GUI; Since then I haven't really tried flashing a different rom since I was busy and haven't really been using the tablet.
Yesterday I downloaded a few roms backed up the current system and tried (with no luck) installing the roms but it gets stuck on the boot logo (I tried the following);
AlienDroidV5.0.1
cm-10-20121101-UNOFFICIAL-otter
cm-10-20121105-1516-otter-sgt7-linaro
jandycane_otter-v1.8.0_0xD34D
jb-kfire-hashcode-10-10
At that point I thought maybe my kindle (somehow) upgraded even though it was showing version 6.2.1 in the settings, so I upgraded the Kernel (I used the following);
fff-u-boot_v1.4a
Then tried installing the ROMs again, with the same problem, I then tried installing the Amazon 6.2.2 (6.2.2-rooted-secureboot) which installed great, worked on the first try...
Yes, I wiped Cache, Develik, Battery and Factory wipe before each rom attempt. I tried using the Kindle Fire Ultimate Utility to kick the tablet out of boot logo loop but the tablet doesn't respond to the commands.
So, can anyone help me out?
Thanks,
Alan
Your recovery is your problem change to twrp. 1.4a is not a kernel it`s a bootloader. huge difference. Pretty sure that most every op of ICS or Jelly Bean has some notation about using twrp to flash the Roms have chosen.
Thepooch said:
Your recovery is your problem change to twrp. 1.4a is not a kernel it`s a bootloader. huge difference. Pretty sure that most every op of ICS or Jelly Bean has some notation about using twrp to flash the Roms have chosen.
Click to expand...
Click to collapse
Just flashed TWRP using http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127 going to check now
Update: Thanks Pooch, that solved the problem... not sure how I missed this huge step, glad I asked.
keroseneman said:
Just flashed TWRP using http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127 going to check now
Update: Thanks Pooch, that solved the problem... not sure how I missed this huge step, glad I asked.
Click to expand...
Click to collapse
No problem bud glad you got it.:good:
Hay guys,
for my Desire HD i use the custom rom Jellytime. I used the r6.2, then i flashed an update.zip to r7.
But then i realized, bluetooth is not working and i'm not connected to my google account. So i decided to downgrade to r6.2, so i flashed the .zip as an update.zip. now my phone freezed after the jellytime bootlogo :/
I tried to get to the recovery but when i press power+ volume down, it vibrates 3 times and nothing happens.
does anybody knows what to do? I have a backup, so are there any possibilities, to restore the backup?
slixx
Ouch, did you flash the ROM as an update.zip or the backup?? And what recovery do you got?
hay,
i flashed the r7 as an update.zip, to update my custom rom from r6.2 to r7. and i also flashed the r6.2 as an update.zip to downgrade
I think this was my fault.
i have the lastes version i think - something like 5.0.1.20.
okay,
i used the adb to boot into the bootloader. with the bootloader i booted into the recovery, know i try to restore my backup.
hope it works!
Report back with your progress.
EDIT: and save yourself some trouble next time by using recovery instead of bootloader for installing ROMs
It worked!
i restored the backup, after this i installed an older version of jellytime, flashed gapps, and restored my personal stuff with google
i didn't flashed the rom with the bootloader. i just forgot to flash gapps, after installing the jellytime update ._.
this was the reason why i was not connected to my google account. and the bluetooth function...hmm i dont care cause i don't use it.
but now everything is okay again.
BTW, if you feel like getting back to jelly time, I recommend using v30, or the last 4.1.2 version of jelly time. I think it was only until v9 that jellytime started getting stable, and v30 should be almost bug free.
Sent from my Inspire 4G using xda app-developers app
black screen after update of Jellytime was installed
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
ektob said:
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
Click to expand...
Click to collapse
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
glevitan said:
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
Click to expand...
Click to collapse
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
ektob said:
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
Click to expand...
Click to collapse
I didn't ask about root, did I? I made 2 simple questions that have not been answered
glevitan said:
I didn't ask about root, did I? I made 2 simple questions that have not been answered
Click to expand...
Click to collapse
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
If so, have you flashed the boot.img in fastboot? I am not sure in this. I think I was give two choices - fast boot and normal boot. I selected normal boot.
ektob said:
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
Click to expand...
Click to collapse
You are wrong in your conclusion.
bananagranola said:
You are wrong in your conclusion.
Click to expand...
Click to collapse
OK..fine. Still I'm sure I'm unlocked. Now I acctally got the bootloader working - ACE PVT ENG S-OFF RL . So I read your link - thanks it seemed valuable but I didn't get why I needed to open a terminal window (dos window I assume) secondly it didn't work at all since the usb connection didn't connect properly.. I'm sorry for being such a hassle.. . I did before though un zip the folders so if needed - where should the boot image be in order for it to load from the sd card ?
Thanks for the patience
EDIT: I tried to follow the flashboot steps as best I could, but failed to load the image.
ektob said:
ACE PVT ENG S-OFF RL
Click to expand...
Click to collapse
Then you are not unlocked!! I give up.
bananagranola said:
Then you are not unlocked!! I give up.
Click to expand...
Click to collapse
Whatever - I didn't stop me from installing other ROMs. This case is now closed - I changed ROM to CodefireX - worked fine. But sure I will look into it if its necessary - for sure for Jellytime..
I must say you guys really tried to help but any reasons to why I have to unlock bootloader - is that something that have become necessary over time? Maybe its also bad instructions on the ROMS main pages? Why do I need to search 50 different forums to get a simple answer?
Anyway you can give up on me now because I resolved it on my own. Thanks
Because there are additional steps if you are unlocked...
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
newgeek- I don't know if the AT&T version of this is very different to my F240 version but I am familiar with that 3rd screen you posted with the "secure booting error" or something like that.
What about just pulling that battery out and doing factory reset and start over from the beginning ?
LL13-
newgeek35 said:
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
Click to expand...
Click to collapse
Try to push another ROM via adb, I read in the general Section that there were some Gummy files that weren't the right size, just download CM11 and try to flash it, TWRP is saying that the flash failed, that's why you are stuck in recovery.
Erik
The phone currently has no OS , I also tried to mount my 64gb sd card to install off of that & It gives me a mounting error for SD CARD. I have tried several other roms & No luck , Keeps giving me FAILED. Is this because of the secure boot perhaps? I'm totally clueless why it's not taking it. I'm running my nexus 4 with the gummy rom without a hitch.
Why not try a different SD card ? If that SD card was in the phone when all this happened maybe something is on the card that's bad ?
LL13-
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
newgeek35 said:
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
Click to expand...
Click to collapse
It looks like an error with the updater script, maybe something twrp isnt reading or executing? try a different rom.
At worst try a different Recovery.
ADDED:2/4/2014: I would avoid twrp on freegee, i've heard others have issues and it may have something to do with your situation.
Also, I noticed your twrp says 2.6.1.0, am I mistaken or is the newest teamwin 2.6.3.1? That number don't look right.
If possible try to flash madmacks twrp or cwm 6.0.4.6.
1.Try to Flash a ROM via sideload
2. you can end the recovery boot loop by using adb commands, there are two methods try them
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
and
http://forum.xda-developers.com/showpost.php?p=48136185&postcount=268
I had the same issue seems like the are some problems with TWRP on this particular phone I flashed the regular clockworkmod and it works perfect.I tried on another phone with same results.
Right now
Flash stock rom
root
use freegee to install regular cwm I tried rom manage but recovery did not installed
the flash another rom if thats what you really want but copy rom directly to sd card instead
Its not just twrp apparently the new update of freegee installs the wrong bootloader/image on our phone. It bootloops anyone that uses it.
Sent from my LG-E980 using XDA Premium 4 mobile app
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Neroga said:
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Madmack's TWRP is reliable when you want to have no bootloops into your recovery. But i have the problem, that i cannot flash any other roms and it shows, that my LG E986 isnt recognized as a suitable device for the rom and it aborts the procedure. Although on the other recoveries it worked fine...
Is there something what i have to do except switching recoveries to my phone's death?
I used ADB to push the stock rom back to device & It took it's sweet time but it worked. I sold the phone to a friend of mine LOL! They wont know the difference.
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.
I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.
That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.
[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse
Thanks.!
i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.
Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life